- Shipped
- October 21, 2026 at 5:25 AM UTC
- Author
- Kamo
- Commit
- 53e6e2c
Always allow: from the decision bar, the approver picks just this action or the whole kind (in plain words), reads exactly what changes in the SI's job description, and confirms; SecurityService writes the rule (preview/grant/revoke relays), then the request is approved and the SI told. Someone who may not change the job description is told why and who can, and may approve once; a right the action needs is offered only to someone who may give it. "Ask me again" in the result and on the rule in the SI's job description takes it back. Why: a follow-up names the earlier request in its own card's words, who decided it and when, with a link; the job description line says which rule asks. Avatar: the chat windows' lookup (fetchMemberAvatar: photo, then picked avatar, initials last) on the card and in the inbox. Colours: the approvals UI paints from --color-primary through ApprovalBrandScope (buttons, chips, focus, badges, progress, alerts, status); words on a brand fill are black or white by the brand's own luminance, so any brand reads at AA. Risk and state keep their semantic colours.