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

Activate ZONE-WP-0001 and decide exception lifecycle

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 13:01:14 +02:00
parent 6f6c893011
commit 11af8095ae
4 changed files with 174 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

17
SCOPE.md
View file

@ -128,16 +128,17 @@ Their answers are binding on this repo and are recorded in the workplan.
---
## Current state (2026-08-19)
## Current state (2026-08-22)
Seeded and reviewed. **No model, no schema, no runtime** — deliberately: an
engine that ships a wire format before it has partitioned the real estate
defines the model by accident.
`ZONE-WP-0001` is active. T01 confirmed ownership, T02 partitioned the estate,
and T04 selected reviewed declarations with enforcement-time expiry: **no
zone-engine runtime is warranted**. The exception lifecycle is recorded in
`docs/exception-lifecycle-2026-08-22.md`.
`ZONE-WP-0001` carries the work. T01 is answered by both owners; T02–T07 are
open. Whether a runtime is warranted is an *output* of T04, and the "no runtime"
answer is a legitimate result that would retire this repo rather than embarrass
it (`GOAL.md` gate 5).
T03 is waiting on a declaration-boundary ruling from `repo-manager` and
`net-kingdom`. The current evidence has nine declared rapp workloads, but only
one of ops-warden's 27 lanes can be joined to one; unknown membership is kept
unknown rather than inferred. No API, storage, or wire schema has been shipped.
---