[IkarusAILabs]

Follow-up to #17. This commit was pushed to the docs/break-glass-strategy branch after #17 had already merged, so it never reached main.

Summary

With a dedicated agent account, only the halt SCP can be applied from outside. ECS tasks, network ACL associations, Lambda concurrency, schedules and the canary can only be changed from inside the agent account, so HaltAI needs an execution role inside the boundary.

• Roadmap 7.1, "Two HaltAI identities":
  • an operator role (outside) and an execution role (inside);
  • six protections that prepare checks, any gap blocking:
    1. an exact-ARN trust policy;
    2. the only exemption from the halt SCP;
    3. a standing protection SCP;
    4. no workload runs as it;
    5. least privilege;
    6. audited use.
  • Claim 3 is extended to cover the execution role.
  • The shared-account variant is marked as weaker.
• Threat model 4.1: the execution role is trusted only while those protections hold; each protection is paired with the threat it addresses; prerequisites are updated.

Issues #20 and #21 already reflect this.

Checks

• All relative links and anchors resolve
• Docs only

🤖 Generated with Claude Code