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

Rule what A12 leaves alone, which text a run names, and one detector for the estate

Browse source 
GH-DEC-2026-021 rules the five questions from the GH-DEC-2026-020 round, with
counts re-measured on disk.

1. A12 reaches a pin, not a citation. A prose revision citation is provenance.
   No declaration changes, gate-house's own included. The narrow reading
   benefits gate-house, so it is drafted as A12 r3 for assent, not
   self-approved.
2. VALIDATED_AGAINST names accepted v0.7 plus the decisions enforced.
   tenant-engine and flex-auth re-point now.
3. ops-warden's playbook detector is the estate reference, with one addition.
   Copies converge by the post-flip re-point commit.
4. The re-point is a post-flip closing condition of GH-WP-0004 (T11), not a
   GH-DEC-2026-019 precondition.
5. whitehat-security's conformance_state moves out of the declaration.
   A single-repository run is admitted as A11 r2.

INFD-IN-0007 and GH-WP-0004-T06 are left open, coupled.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 12:39:57 +02:00
parent d8c82a8bb4
commit 39d9287596
3 changed files with 302 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

29
workplans/GH-WP-0004-section-11-layer-declarations.md
View file

@ -114,6 +114,10 @@ state_hub_task_id: "8dd32a14-35d9-55c3-adfa-d9c728b550b1"
Asked, not enrolled. Its correction from `surface` to `Staff`/`pep-shaped` is its own and
is not a condition of this task.
Answered **yes** by `informed-decision` (`docs/section-4-catalog-row.md`). The row is not
drafted yet: it is coupled to `INFD-IN-0007` (how §3.4's Staff definition fits a
deterministic repository that holds evidence), which is left open by `GH-DEC-2026-021`.
```task
id: GH-WP-0004-T06
status: todo
@ -155,6 +159,12 @@ Returns so far: `approval-engine` assents to A9–A13 as first circulated (98d33
re-circulated 2026-09-21 to the round list with `GH-DEC-2026-020`; assent to r2 is asked
afresh from every round member, including `approval-engine`.
A12 r2 returns: `approval-engine` approved; `kings-guard` revised (KG-DEC-2026-005, prose
citations; A11 single-repository scope); `audit-core`, `access-engine` (`flex-auth`) and
`ops-warden` deferred assent to the operator, which is pending and not refused.
`GH-DEC-2026-021` rules both findings. The set is now v0.3, with **A11 r2 and A12 r3**
re-circulated 2026-09-21. Assent to the earlier texts does not carry over.
```task
id: GH-WP-0004-T09
status: progress
@ -174,7 +184,24 @@ priority: medium
state_hub_task_id: "34d0582b-9b7e-5dcf-ac1e-0257312b8b7b"
```
### T11 — Post-flip: all eight checkers name v0.8 and run the reference detector
A post-flip closing condition, not a condition on the flip (`GH-DEC-2026-021` §4). The
following re-point `VALIDATED_AGAINST` to the accepted v0.8 and converge their copies on the
reference detector in `ops-warden`'s playbook (`GH-DEC-2026-021` §3), or record a dated
reason in writing: `kings-guard`, `user-engine`, `zone-engine`, `secrets-engine`,
`maturity-engine`, `ops-warden`, `tenant-engine` and `flex-auth`. The T10 flip notice names
all eight. `whitehat-security`'s move of `conformance_state` out of its declaration is
tracked here with the same deadline.
```task
id: GH-WP-0004-T11
status: wait
priority: medium
```
## Done when
All five amendments are in the v0.8 cut, the three `GH-DEC-2026-019` closing conditions
are met, and `net-kingdom` has flipped v0.8 to `accepted`.
are met, `net-kingdom` has flipped v0.8 to `accepted`, and T11's post-flip re-point is
done.