tegwick
718591919e
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
391 lines
20 KiB
Markdown
391 lines
20 KiB
Markdown
---
|
||
id: GH-WP-0004
|
||
type: workplan
|
||
title: "§11 layer declarations — amendment set and estate closure"
|
||
domain: infotech
|
||
repo: gate-house
|
||
status: active
|
||
flavor: implementation
|
||
origin: GH-IN-0003
|
||
owner: codex
|
||
topic_slug: infotech
|
||
created: "2026-09-21"
|
||
updated: "2026-10-11"
|
||
state_hub_workstream_id: "59481e51-2792-5f2c-99c8-2732a0561939"
|
||
---
|
||
|
||
# §11 layer declarations — amendment set and estate closure
|
||
|
||
## Goal
|
||
|
||
Land the five §11/§4/§3 amendments that `GH-DEC-2026-017` and `GH-DEC-2026-018`
|
||
produce, into the **proposed** v0.8 cut before the acceptance flip, and close the
|
||
estate-side items the two rulings create. `GH-DEC-2026-019` holds the flip on this
|
||
workplan and states three closing conditions.
|
||
|
||
**Normative text for A9–A13 is drafted at
|
||
`docs/amendments/v0.8-section-11-declaration-amendments.md`.** That file is the
|
||
reviewable unit: each amendment carries its own wording, defect statement, and
|
||
authority, so it can be argued before anything touches the cut.
|
||
|
||
## Why now
|
||
|
||
`access-engine`'s boundaries review (`FLEX-WP-0030`) found five §11 defects from
|
||
outside, after the v0.8 round closed, in the section `audit-core` was asked to attack
|
||
and did not return a review on. One of them — A10's — is `gate-house`'s own amendment
|
||
`A2`, written twelve days ago and reviewed twice without anyone noticing it named a §4
|
||
property §4 does not carry.
|
||
|
||
v0.7 stays `accepted` and in force, unpatched. Nothing operational waits on this; the
|
||
cost of the hold is documentation currency, which is what makes it affordable
|
||
(`GH-DEC-2026-019` §3).
|
||
|
||
## Tasks
|
||
|
||
### T01 — A9: state the §3 vocabulary once, as tokens
|
||
|
||
Four tokens, closed, case-insensitive comparison, `Engine` not `Engines`, role is not
|
||
layer. Resolves the §3-versus-§4 divergence that makes two faithful runs disagree about
|
||
eight rows.
|
||
|
||
```task
|
||
id: GH-WP-0004-T01
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "8b4042db-d827-5788-9a08-71e351375f05"
|
||
```
|
||
|
||
### T02 — A10: §4 gains an evidence-source marking; §11's check reads the marking
|
||
|
||
Includes the per-event-class clause and the count repair. Then assess the remaining §4
|
||
rows repository by repository — `access-engine` is marked by `GH-DEC-2026-018` §2; the
|
||
others are asked, not assigned.
|
||
|
||
```task
|
||
id: GH-WP-0004-T02
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "813b00f4-1d72-5530-8777-c7983a2559ad"
|
||
```
|
||
|
||
### T03 — A11: `INTENT.md` governs, the sidecar is derived, a run states its scope
|
||
|
||
```task
|
||
id: GH-WP-0004-T03
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "7735233f-864f-5a73-9b60-7399995b5b97"
|
||
```
|
||
|
||
### T04 — A12: a declaration carries no standard version
|
||
|
||
Includes asking `ops-warden` to drop `standard_version` from the reference form rather
|
||
than each of the seven adopters deciding separately.
|
||
|
||
**Revised as A12 r2 (2026-09-21, `GH-DEC-2026-020`).** Applying A12 split thirteen
|
||
repositories on its reach. r2 states that it reaches every key and value of the declaration
|
||
(a version-bearing `standard:` path and `companion_version` included), does not reach stance,
|
||
claims or classification maps, and puts the version in the run's output rather than in a
|
||
record every repository must emit. Required per-repository changes are listed in
|
||
`GH-DEC-2026-020` §1, §2 and §4. r2 is re-circulated under T09; assent to A12 as first
|
||
circulated does not carry over.
|
||
|
||
```task
|
||
id: GH-WP-0004-T04
|
||
status: done
|
||
priority: medium
|
||
state_hub_task_id: "d40253b6-cdee-5ec3-960a-81a24cdd1947"
|
||
```
|
||
|
||
### T05 — A13: the `access-engine` coordinate is pending, not broken
|
||
|
||
One line in §4. No gate-house ruling required; substance already ruled in the owning
|
||
repository under `FLEX-WP-0020`.
|
||
|
||
```task
|
||
id: GH-WP-0004-T05
|
||
status: done
|
||
priority: low
|
||
state_hub_task_id: "8dd32a14-35d9-55c3-adfa-d9c728b550b1"
|
||
```
|
||
|
||
### 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.
|
||
|
||
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`.
|
||
|
||
2026-10-03 (CUST-WP-0075 inbox sweep): `informed-decision`'s 2026-09-27 reply approves A11 r2
|
||
and A12 r3 (operator-authorized; recorded under T09), changes no files, and confirms
|
||
`INFD-IN-0007` and the §4 row coupling stay open with no deadline. Nothing the task waits
|
||
for was delivered; the wait stays on `informed-decision` resolving `INFD-IN-0007`.
|
||
|
||
2026-10-03 (CUST-WP-0075, second check): `informed-decision`'s 2026-10-03 message (`6ab42744`,
|
||
INFD-WP-0005 doctrine check on frictionless decision intake) is about memo admission, not
|
||
`INFD-IN-0007` or the §4 row. It was answered separately (reply `4a290496`; draft
|
||
`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.
|
||
|
||
2026-10-11: Gate House prepared proposal `GH-WP-0004-T06-r1` in
|
||
[the bounded doctrine packet](../docs/amendments/informed-decision-staff-evidence-disposition-proposal.md)
|
||
and an unsigned [founder memo draft](../docs/decision-memos/2026-10-11-staff-evidence-tension.memo.json).
|
||
Recommended disposition is an explicitly carried §3.4 tension and the requested
|
||
Staff/PEP-shaped/evidence-source yes catalogue row, with unmet emission guarantees
|
||
reported honestly. Exact candidate text and alternatives are reviewable. No founder
|
||
answer, source-owner assent, model publication or runtime evidence is inferred;
|
||
INFD-IN-0007 and T06 remain open pending real disposition and row handoff.
|
||
|
||
2026-10-11 (confirmed human disposition): native memo
|
||
`infd-20261011-staff-evidence-tension@1`, review
|
||
`review-2e615985-54c9-40d8-8547-b8fdcb10b1d6`, is confirmed ACCEPT, non-stale,
|
||
by human platform-root at 01:46:25Z; approval
|
||
`d90c899b-f25c-4e66-a003-808ee5b1324f`, disposition
|
||
`disp-24e94200-ed93-4a18-900c-3128d26ba212`.
|
||
Recorded as `GH-DEC-2026-025`, pinned to original proposal SHA256
|
||
`08bc78a29c2b67cec0aafba993fb2d25312b629ecccb81458980baafe38e566a`
|
||
and exact submission `d2224fb5f8e577b1dd45b73fb01bf6c8880f1e7e167945e3a186b23738742609`.
|
||
The [exact candidate row/text handoff](../docs/amendments/2026-10-11-staff-evidence-disposition-handoff.md)
|
||
is prepared for NetKingdom source-owner follow-through. Acceptance is only the
|
||
bounded doctrine disposition, not whole v0.9 ratification, accepted-v0.8 edit or live
|
||
execution. T06 stays progress pending real publisher receipt/standard-voice adoption;
|
||
INFD-IN-0007 and the Staff finding are not closed from a human memo alone.
|
||
Per-event emission obligations stay with their existing source-owner records.
|
||
|
||
```task
|
||
id: GH-WP-0004-T06
|
||
status: progress
|
||
priority: medium
|
||
state_hub_task_id: "62ac1f55-d3fc-59bd-84a5-8baec5de6bac"
|
||
```
|
||
|
||
### T07 — Closing condition 2: `audit-core` returns its §11 review or declines in writing
|
||
|
||
A written decline closes it. §14 records *not claimed* rather than counting silence as
|
||
assent, and the point is that the record says which.
|
||
|
||
2026-10-03 (CUST-WP-0075 inbox sweep): `audit-core` **returned** its §11 review on 2026-09-23
|
||
("returned, not declined"; `audit-core` history/2026-09-23-v0.8-section-11-review.md), which
|
||
closes closing condition 2. It carries two findings against the cut — the explicit
|
||
completeness non-claim should bind load-bearing as well as attributive emission guarantees,
|
||
and A10's evidence-source column needs three values (`yes` / `no` / `unassessed`) with
|
||
`audit-core` marked `no`. Their disposition is tracked in T12, not here.
|
||
|
||
```task
|
||
id: GH-WP-0004-T07
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "eb459f71-a163-5920-b2fb-63d97d225952"
|
||
```
|
||
|
||
### T08 — Closing condition 3: `key-cape`, `ops-mason`, `net-kingdom` declare or record a dated gap
|
||
|
||
`gate-house`'s own is discharged (`GH-DEC-2026-017` §6, this commit). A declaration or a
|
||
dated gap satisfies this equally; conformance is not the condition.
|
||
|
||
2026-10-03 (CUST-WP-0075 inbox sweep): all three have declared, none needed a gap.
|
||
`key-cape` declared `layer: Tooling`, `role: —` in INTENT.md frontmatter (key-cape 9cb9507,
|
||
reply 2026-09-21); `ops-mason` declared `layer: Staff`, `role: pep-shaped` (ops-mason 0ff263a,
|
||
now on origin/main, reply 2026-09-21; it records its §5.3 tooling contacts as dated gaps);
|
||
`net-kingdom`'s 2026-09-23 reply confirms its bare `layer: Taxonomy` declaration satisfies
|
||
A12 r2/r3. All three verified in the local checkouts. Closing condition 3 is met.
|
||
|
||
```task
|
||
id: GH-WP-0004-T08
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "b512f842-f061-53b3-b6f4-a1618db3ff37"
|
||
```
|
||
|
||
### T09 — Circulate A9–A13 for assent and disposition the returns
|
||
|
||
Round list: `net-kingdom` (publisher), `access-engine`, `audit-core`, `approval-engine`,
|
||
`ops-warden`, `kings-guard`, plus `informed-decision` and `railiance-master` as the two
|
||
repositories the vocabulary ruling touches from outside §4.
|
||
|
||
Returns so far: `approval-engine` assents to A9–A13 as first circulated (98d337c4). A12 r2
|
||
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.
|
||
|
||
2026-10-03 (CUST-WP-0075 inbox sweep): A11 r2 / A12 r3 returns now in — `audit-core`
|
||
approved (2026-09-23, founder's disposition in its voice), `net-kingdom` approved (A11 r2
|
||
fresh; A12 r3 by operator decision, net-kingdom@a7a4db5), `informed-decision` approved
|
||
(2026-09-27, operator-authorized), and the operator's 2026-09-21 disposition stands as the
|
||
return for `access-engine` and `ops-warden`. Still outstanding and theirs to give:
|
||
`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: done
|
||
priority: high
|
||
state_hub_task_id: "ea3e5868-74c8-5893-b514-f60abdaaf42f"
|
||
```
|
||
|
||
### T10 — `net-kingdom` assembles the amendments into the v0.8 cut and flips acceptance
|
||
|
||
Publication and the flip are `net-kingdom`'s and were handed over at v0.8 round close.
|
||
This task tracks the handoff, not the execution.
|
||
|
||
2026-10-03 (CUST-WP-0075 inbox sweep): `net-kingdom` (2026-09-23) recorded A11 r2 and A12 r3
|
||
in the v0.8 §11 set and confirmed the flip notice will name the eight T11 checkers; the hold
|
||
under `GH-DEC-2026-019` stands and v0.8 is not flipped. The flip now waits on T09's remaining
|
||
returns and on T12 (audit-core's findings are against the cut), then on `net-kingdom`.
|
||
|
||
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: done
|
||
depends_on: [GH-WP-0004-T09, GH-WP-0004-T12]
|
||
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.
|
||
|
||
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: done
|
||
depends_on: [GH-WP-0004-T10]
|
||
priority: medium
|
||
state_hub_task_id: "1643517b-96e5-5cad-bbe0-0207189e352c"
|
||
```
|
||
|
||
### T12 — Disposition `audit-core`'s §11 review findings and its §9.6 exception question
|
||
|
||
Added 2026-10-03 (CUST-WP-0075 inbox sweep). `audit-core`'s returned review (T07) carries two
|
||
findings against the cut: (1) the completeness non-claim should be required for load-bearing
|
||
as well as attributive emission guarantees in §11; (2) A10's evidence-source marking needs
|
||
`yes` / `no` / `unassessed`, with `audit-core` marked `no` (`GH-DEC-2026-018`, `AUDIT-IN-0005`).
|
||
Separately, `audit-core` asked on 2026-09-24 (`AUDIT-IN-0006`, from `FLEX-DEC-2026-018`) whether
|
||
§9.6 admits a declared, detectable, direction-limited failure-path release exception for a
|
||
load-bearing source, and whether §11 should read it. gate-house replied 2026-10-03 with the
|
||
reading of the current text (no exception admitted; §11 reads no such declaration; the
|
||
conflict with fail-closed is gate-house's to resolve) and deferred the ruling to a decision
|
||
record. Rule all three via `rmgr decision create`, amend the set, and re-circulate as needed.
|
||
|
||
2026-10-05: ruled as `GH-DEC-2026-024`. (1) The completeness non-claim binds load-bearing
|
||
sources as well as attributive ones, where the declared guarantee is not itself completeness;
|
||
A2 is amended. (2) A10's evidence-source column is `yes` / `no` / `unassessed`, and
|
||
`audit-core` is `no`. (3) A §9.6 exception for a declared, detectable, direction-limited
|
||
failure-path release is refused; §11 gains no declaration for it. v0.8 is not flipped.
|
||
Publication remains net-kingdom's under T10. T09 stays wait.
|
||
|
||
```task
|
||
id: GH-WP-0004-T12
|
||
status: done
|
||
priority: high
|
||
state_hub_task_id: "8585b3e2-f858-5e10-8f42-abfd2a36d428"
|
||
```
|
||
|
||
## Done when
|
||
|
||
All five amendments are in the v0.8 cut, the three `GH-DEC-2026-019` closing conditions
|
||
are met, `net-kingdom` has flipped v0.8 to `accepted`, and T11's post-flip re-point is
|
||
done.
|