coulomb/zone-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: close operator config migration evidence

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0291a-1e87-7151-9934-fcbfe3f65eb1
This commit is contained in:
tegwick 2026-08-22 15:51:03 +02:00
parent 4b908e7189
commit d6e74a55f6
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/evidence/security-zone-adoption-2026-08-22.md
View file

@ -27,11 +27,11 @@
`decision:f3f7c88f9585582a`. Only token length and a truncated fingerprint
were emitted.
The operator's persistent `warden.yaml` still contains the two retired keys.
The live proof used a temporary migrated copy; no operator configuration was
overwritten. Until those lines are removed, the new loader rejects that file
with an explicit migration error rather than silently selecting a second
policy source.
The operator's `warden.yaml` was migrated from the two retired keys to the
compiled `zone_registry_path`. The live proof was then repeated successfully
against that real configuration. The new loader continues to reject either
retired key with an explicit migration error rather than silently selecting a
second policy source.
The exception-lifecycle evidence in
`docs/exception-lifecycle-2026-08-22.md` establishes that expiry is evaluated