autonomy record ok: 2 signed change(s) in policy/autonomy-changes.jsonl
  evidence  receipts/three-words.receipts.jsonl (5 rows, chain verified)
  evidence  receipts/mu-ai-011.receipts.jsonl (10 rows, chain verified)
  evidence  receipts/autonomy-window.receipts.jsonl (3 rows, chain verified)
  AC-2026-0914-01  DEMOTION  pre_position_crew  L1-approval-required -> L0-never-autonomous
      trigger verification-failed  effective 2026-09-14T20:05:00Z  approved_by Distribution Operations (Mgr. L. Tran)
      receipts AR-70F1321A077D
      signature 395f2d3df786e348e0c58edb6122d19e...
  AC-2026-0922-01  promotion pre_position_crew  L0-never-autonomous -> L1-approval-required
      trigger clean-evidence-window  effective 2026-09-22T15:00:00Z  approved_by Distribution Operations (Mgr. L. Tran)
      receipts AR-81A39C8D6B0A, AR-FCAA73709D42, AR-B87F91925C7B
      signature 2fce0988ab1154a504e421bec8d9ae8e...
  in force  pre_position_crew L1-approval-required - and policy/envelope.json runs it there too
  the guard reads its starting mapping from policy/envelope.json; this record is what authorizes a change to it - a record change, not a config change
