- Shipped
- November 7, 2026 at 3:00 AM UTC
- Author
- Kamo
- Commit
- fa07b47
Owner decision 2026-11-07 on SIE3's finding: once a run has read outside content (email, web page, document, text, call, meeting), a send to a new recipient, a delete, an external share, a settings change, money and shell commands wait for a person's approval for the rest of the run, whatever the charter makes autonomous. A reply to the person the run is conversing with (identity counterparty) or a plain reply to the email the run read stays automatic. An authenticated direct order of a supervisor in the SI's chain of command (SecurityService standing, or acting on their account) stands (No Insubordination); its scope and the never-grantable/human-only rules still apply. One rule in the policy decision point: OUTSIDE_CONTENT (ASK with the act as reason; LIFT SUPERVISOR_ORDER/ON_BEHALF; PASS **************** plain-language record explanation and approval card ("This task read an outside email; a person should OK sending to a new address."). Goldens: injection-gates.txt re-pinned (16 lines: EMAIL/DOCUMENT/CHAT/SMS sends and deletes now ask); SIE2 pipeline-scenarios.txt +180 appended tainted scenarios and tool-static-decisions.txt +88 appended per-tool act lines; every earlier SIE2 line unchanged.