- Shipped
- October 4, 2026 at 7:23 PM UTC
- Author
- Kamo
- Commit
- feda231
When the charter asks for approval and the AI cites a verified request (onRequestOf), K3 is asked with mode ON_REQUEST, the requester and the reference. An APPROVED row lets the action run at once; it still passes the limits and the outreach gate, and what it came to is reported on K3b (EXECUTED, or FAILED with its status and message, before the key is freed). An ambiguous outcome is left to the tick, which re-executes under the same key. K3's NOT_AN_APPROVER, REQUEST_USED and SHADOW, a soft refusal and a SHADOW charter ask a person as before, and the answer says why (onRequestOf {accepted:false, reason}). FORBIDDEN still refuses, and an action that needs no approval writes no ON_REQUEST row. A dry run asks K3 under X-Kamo-Dry-Run and writes nothing. A re-executed ON_REQUEST approval keeps the outreach gate (K4 mode).