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

Close verified v0.8 source flip and eight-owner checker returns

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
This commit is contained in:
tegwick 2026-10-11 02:21:40 +02:00
parent 320d254c35
commit 8e7f012326
3 changed files with 599 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -4,13 +4,13 @@ type: workplan
title: "§11 layer declarations — amendment set and estate closure"
domain: infotech
repo: gate-house
status: blocked
status: active
flavor: implementation
origin: GH-IN-0003
owner: codex
topic_slug: infotech
created: "2026-09-21"
updated: "2026-10-05"
updated: "2026-10-11"
state_hub_workstream_id: "59481e51-2792-5f2c-99c8-2732a0561939"
---
@ -109,7 +109,7 @@ priority: low
state_hub_task_id: "8dd32a14-35d9-55c3-adfa-d9c728b550b1"
```
### T06 — Ask `informed-decision` whether it should become a §4 catalog row
### T06 — Resolve the Gate House §3.4 doctrine question, then disposition the requested §4 row
Asked, not enrolled. Its correction from `surface` to `Staff`/`pep-shaped` is its own and
is not a condition of this task.
@ -129,11 +129,23 @@ INFD-WP-0005 doctrine check on frictionless decision intake) is about memo admis
`decisions/drafts/GH-DEC-2026-023-frictionless-decision-intake.md`). No other
`informed-decision` message delivers the gate. The wait stands.
2026-10-10 (security consolidation, Gate House owner recording): the external answer
is already complete. `informed-decision/INTENT.md` (Layer declaration, unresolved question)
and `informed-decision/docs/section-4-catalog-row.md` §§1, 3, 5 state both the affirmative
request and its evidence obligations. `GH-DEC-2026-021`, “What this does not rule”,
explicitly assigns the remaining answer to §3.4 doctrine: amend that definition or state
a carried tension in the standard’s voice. Gate House owns that doctrine; requiring
`informed-decision` to resolve it was a stale ownership assignment.
Retargeted to Gate House preparation and disposition of the §3.4 question, then handoff
of the requested §4 row to net-kingdom. This records no doctrine ruling, human decision,
row publication or emission guarantee. `INFD-IN-0007` and the missing row stay open.
The question remains outside the §11 acceptance hold (`GH-DEC-2026-019` §5 and
`GH-DEC-2026-021`); T10 must not acquire it as a new flip condition.
```task
id: GH-WP-0004-T06
status: wait
blocked_on: message-from:informed-decision
blocking_reason: "informed-decision answered yes; its section-4 row is coupled to INFD-IN-0007, still open with no deadline (reply 2026-09-27; rechecked 2026-10-03)."
status: todo
priority: medium
state_hub_task_id: "62ac1f55-d3fc-59bd-84a5-8baec5de6bac"
```
@ -200,12 +212,31 @@ return for `access-engine` and `ops-warden`. Still outstanding and theirs to giv
`approval-engine`, `kings-guard`, `railiance-master` (no r2/r3 return in the inbox). Wait
re-qualified from `audit-core` to the outstanding members.
2026-10-10 (security consolidation): all three missing owners returned fresh technical
reviews of **A11 r2 / A12 r3**, exact source
`docs/amendments/v0.8-section-11-declaration-amendments.md`, SHA-256
`9b454b83c9aeed08ba13dba4d812f5ae6b4293ced9e43088d64cc3cc00b1459d`.
The Gate House worker read the exact text and each distinct owner return, confirmed
its INTENT basis, own work item, approval disposition and review scope. Each resolves
the owner’s earlier revision-specific question; no remaining technical objection is
claimed for these two amendments. This discharges T09’s missing-return condition.
| Owner source | Owner work item | Review SHA-256 |
| --- | --- | --- |
| [kings-guard technical return](../../kings-guard/docs/reviews/2026-10-10-a11-r2-a12-r3.md) | `KG-WP-ADHOC-2026-10-10-T01` | `eb0bf102653707f5c80f4594df1427ef70f65ed3686abc824418fa19ab9983bb` |
| [approval-engine technical return](../../approval-engine/docs/reviews/2026-10-10-gate-house-a11-r2-a12-r3-owner-review.md) | `APPROVAL-WP-ADHOC-2026-10-10-T01` | `978527d58222bd14fb20cbe963eb87cad49dfd4a8b2dfa420ee102b5ffb4d002` |
| [railiance-master technical return](../../railiance-master/docs/reviews/2026-10-10-gate-house-a11-r2-a12-r3-owner-review.md) | `RMASTER-WP-ADHOC-2026-10-10-T01` | `ee3739febdd9346537ff9892dd0bf2f086544a42e3e65275f5342edc8f23ef84` |
These are owner technical reviews under the accepted Custodian
`canon/standards/delegated-owner-review_v0.1.md`, not founder decisions or publisher
acceptance. Earlier recorded operator dispositions remain history; these returns are
not substituted for them. T10 still requires net-kingdom publication/acceptance; T11
still waits for the actual flip. Accepted v0.7 remains the statute in force.
```task
id: GH-WP-0004-T09
status: wait
blocked_on: message-from:kings-guard
status: done
priority: high
blocking_reason: "A11 r2 / A12 r3 returns outstanding from kings-guard, approval-engine and railiance-master; all others returned approved."
state_hub_task_id: "ea3e5868-74c8-5893-b514-f60abdaaf42f"
```
@ -222,12 +253,32 @@ returns and on T12 (audit-core's findings are against the cut), then on `net-kin
2026-10-05: T12's disposition is recorded (`GH-DEC-2026-024`). T09's remaining returns and
the net-kingdom flip remain. v0.8 is not flipped; the hold under `GH-DEC-2026-019` stands.
2026-10-10: T09’s exact-revision technical returns are complete and T12’s existing
ruling remains recorded. The next action belongs to net-kingdom: assemble/verify the
amended cut and provide its publication/acceptance record. Gate House records neither
the flip nor a human ratification here; the hold is not discharged by technical returns
alone. T06’s separate §3.4 question remains outside this §11 hold.
2026-10-11: confirmed native human memo `infd-20261010-security-layer-v08`,
version 2, accepts exact proposed source SHA256
`103a635f19ab9fe53094d69c3eeebcccd8e87ac9588846167e7e204a7c6de167`.
Approval `8432d0dc-adc0-42d0-9a5b-6b71ff492e15` and disposition
`disp-43e051e9-b12f-4c34-b26e-40b85a96c2e8` are confirmed, non-stale,
accepted at 2026-10-10T23:23:53Z. NetKingdom records source publication
acceptance in `docs/security-layer-v0.8-acceptance.md`; its accepted artifact
SHA256 is `3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b`.
Only acceptance frontmatter and §14 notice were added to the approved normative
cut. T09, T07/T12 and T08 discharge the three GH-DEC-2026-019 closing conditions;
T06 remains separate. This completes the source acceptance handoff tracked by
T10. It grants no live deployment or credential authority. PolicyNexus serving
release is separate and is not T10's publisher-acceptance condition. The
[recording receipt](../docs/evidence/2026-10-11-v0.8-source-acceptance.md)
distinguishes source acceptance from serving publication.
```task
id: GH-WP-0004-T10
status: wait
status: done
depends_on: [GH-WP-0004-T09, GH-WP-0004-T12]
blocked_on: message-from:net-kingdom
blocking_reason: "T12 disposition is recorded (GH-DEC-2026-024). net-kingdom flips v0.8 once T09 returns; the hold under GH-DEC-2026-019 stands. v0.8 is not flipped."
priority: medium
state_hub_task_id: "34d0582b-9b7e-5dcf-ac1e-0257312b8b7b"
```
@ -242,11 +293,41 @@ reason in writing: `kings-guard`, `user-engine`, `zone-engine`, `secrets-engine`
all eight. `whitehat-security`'s move of `conformance_state` out of its declaration is
tracked here with the same deadline.
2026-10-11: the accepted source unblocks post-flip migration. Eight checker
changes and the WhitehatSecurity declaration-state relocation are prepared
in their owner sources. T11 stays progress until their applied source changes,
reference pin/provenance semantics and actual owner check outputs are recorded.
PolicyNexus serving release is a separate publication delivery gate, not an
additional T11 checker condition. No migration is counted from staging alone.
2026-10-11 (applied-source verification): all eight named checkers now
reference accepted v0.8, exact canonical SHA256
`3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b`,
and their actual owner runs record scope. All 40 applied migration paths match
the reviewed manifest hashes. Python owner checker/test receipts pass for
KingsGuard, UserEngine, ZoneEngine, SecretsEngine, MaturityEngine, OpsWarden
and TenantEngine. UserEngine's first test attempt lacked pytest in its owner
venv; the corrected actual command with `PYTHONPATH=src` passes 33 tests.
AccessEngine's actual Go layer package tests pass and its executable detector
reports accepted v0.8, exact digest, scope and PASS. The shared reference
semantics retain pin rejection, authoritative INTENT, derived-sidecar
provenance and disagreement findings; historical negative version fixtures
remain intentional detector inputs. WhitehatSecurity's applied declaration
contains no conformance_state; its dated evidence preserves blocked-clean,
SCOPE links that evidence and its three actual declaration tests pass.
The [self-contained applied-source receipt](../docs/evidence/2026-10-11-v0.8-post-flip-checker-closure.json)
retains actual commands/results, setup correction and all applied file hashes.
This discharges T11's post-flip migration condition. It establishes the stated
source checks, not whole-estate conformance, native capability acceptance,
complete audit emission or a served PolicyNexus publication. T06 remains todo
under Gate House doctrine; GH-WP-0004 remains active until that separate task
has a real disposition.
```task
id: GH-WP-0004-T11
status: wait
status: done
depends_on: [GH-WP-0004-T10]
blocking_reason: "Post-flip condition: the eight checkers re-point to accepted v0.8."
priority: medium
state_hub_task_id: "1643517b-96e5-5cad-bbe0-0207189e352c"
```