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

docs(STATE-WP-0079): retirement freeze policy, close T01
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
States the four admissible reasons for a change to state-hub during
retirement -- preserve compatibility, enable extraction, reduce scope, fix
operational risk -- and the inadmissible case: establishing new permanent
ownership in the component being retired.

The operative test is 'where does this live after cutover?', not 'is this a
good change?' Most inadmissible changes are good changes; STATE-WP-0080's
retarget to RMGR-WP-0004 is the worked example.

Enforced by review rather than new automation: a freeze-checker built inside
State Hub would itself be new permanent automation here, so the policy would
violate itself. New tables/routes/MCP tools are the one hard stop.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-20 07:20:56 +02:00
parent 93e95f93e7
commit 64b71320e7
3 changed files with 104 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/work-record-quality-gates.md
View file

@ -3,7 +3,8 @@
Status: active convention (STATE-WP-0076 policies; STATE-WP-0077 recording + soft visibility)
Related: `dashboard/src/docs/work-records.md`, `policies/intake-doc.md`,
`policies/work-item-dor.md`, `policies/workstream-dod.md`,
`policies/repo-doi.md`, `policies/service-dom.md`
`policies/repo-doi.md`, `policies/service-dom.md`,
`policies/retirement-freeze.md`
## Purpose