- Shipped
- October 21, 2026 at 3:24 AM UTC
- Author
- Kamo
- Commit
- a83f2a1
Owner order 2026-10-20: the Interaction Center's Approvals tab and the approval popups showed members GUIDs and JSON. Every approval now reads as a card a non-technical person understands: the SI's face and name, one sentence of what it wants to do ('Missir Juan Jesus wants to mark the task “Call back Jane about the appraisal” as done'), the records it touches as chips that open them, the exact message it will send (email, text, chat, call, meeting), the details as labelled fields (money, times in the reader's zone, phones and addresses as their popups), why it is asking, the risk in plain words, what approving and declining do, and a countdown to when it lapses. The raw request sits only under a closed Technical details. Approve, decoder with a note, ask the SI in a chat, and edit the wording before approving where the server allows it; A / D / E shortcuts. The inbox (Interaction Center tab, and the Workforce hub with a reading pane beside the list): search, filters by kind and risk, sorting (soonest to lapse first), multi-select with Approve all / Decoder all (high-risk ones named first), quick approve and decoder on each row (a high-risk request opens instead), keyboard navigation, optimistic rows that leave as they are decided, loading skeletons and a warm empty state; Framer Motion under MotionConfig reducedMotion=user, CSS transitions with their own query; light and dark; phone layouts. Strings in the dictionary (pushed first); a phrase the dictionary lacks or that drifted from the server falls back to the server's English, never a key.