ASI Safety Week: Receipts, Rollbacks, and UX That Explains Itself

What Safety Week covers

• Day 1: Define autonomy budgets (latency, cost, data scopes) and bake them into policy-as-code.
• Day 2: Add receipts UI patterns that show users every data source and decision.
• Day 3: Run eval suites with attack prompts and red-team rotations.
• Day 4: Practice reversible launches with kill switches, canaries, and rollback scripts.
• Day 5: Ship the story—publish the “why we trust this agent” note for stakeholders.

Templates inside

We included policy packs, receipts UI snippets, eval YAML, and launch comms you can paste directly into PRs and executive updates.