- Ya
- 12 Agosti 2026, 15:18 UTC
- Mwandishi
- kamo
- Ahadi ya
- e2c6661
Being off the clock while at work is the state that costs someone money, and it was the one state nothing announced: the indicator was simply absent, and an absence is not a signal. The control now carries a breathing red glow whenever the member is clocked out. A breathing glow on a 1.8s cycle rather than a hard blink. That is well under the three-flashes-per-second photosensitivity threshold, and a strobe in the corner of every screen would be intolerable for the eight hours a day it is meant to be visible. Under prefers-reduced-motion the glow is held STEADY rather than removed — unlike the obligation ring next to it, the motion here is not redundant with a badge or a count, so removing it would remove the only signal. The glow only appears once the state is actually KNOWN. Painting it during the first fetch, or mid-punch while the optimistic toggle settles, would announce a problem that may not exist, and a warning that cries wolf on every page load is one people learn to stop seeing. The clocked-in dot is green instead of --accent-people. That token is the HRS module's amber identity tint (#c47d1a), which reads as a warning sitting next to a red glow — on the clock is the good state and has to look like it. The trailing bullet is gone. It carried no information the dot did not already carry, and it took the .tabular !important workaround with it. overflow is pinned visible on the button rather than inherited: the glow sits at a negative inset, so a clipping ButtonBase would swallow it entirely and the control would look merely unstyled rather than broken — the hardest kind of visual bug to notice.