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

docs: plan zone reference contract hardening

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-23 11:29:20 +02:00
parent 5ce5117506
commit 1a20bd6ba2
3 changed files with 334 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

13
SCOPE.md
View file

@ -14,11 +14,10 @@ exception semantics. It does **not** run an engine or make policy decisions.
## Current lifecycle
The repository's only workplan, `ZONE-WP-0001`, is finished and has `DoD-Ok`.
All seven tasks are done. The standard is published in `net-kingdom`, two
workload owners have adopted it, a third repository has read the declarations,
ops-warden's global policy switch is retired, and the no-runtime decision is
recorded.
The delivery workplan, `ZONE-WP-0001`, is finished and has `DoD-Ok`. All seven
tasks are done. The standard is published in `net-kingdom`, two workload owners
have adopted it, a third repository has read the declarations, ops-warden's
global policy switch is retired, and the no-runtime decision is recorded.
Those facts satisfy `GOAL.md`'s success gates and retirement condition. This
repository is therefore **complete and an archive candidate**, not an active
@ -26,6 +25,10 @@ service backlog. Keeping it writable is useful only while the estate wants a
reference implementation and the evidence history here; canon remains the
published source for consumers.
`ZONE-WP-0002` is a ready follow-up hardening plan. It does not reopen the
runtime decision: it makes canon lineage, reference output, owner provenance,
conformance fixtures, and the final archive-or-retain choice explicit.
## Capability actually present
This repository contains: