gate-house/workplans/GH-WP-0004-section-11-layer-declarations.md

id	type	title	domain	repo	status	flavor	origin	owner	topic_slug	created	updated	state_hub_workstream_id
GH-WP-0004	workplan	§11 layer declarations — amendment set and estate closure	infotech	gate-house	active	implementation	GH-IN-0003	codex	infotech	2026-09-21	2026-09-21	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.

id: GH-WP-0004-T01
status: todo
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.

id: GH-WP-0004-T02
status: todo
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

id: GH-WP-0004-T03
status: todo
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.

id: GH-WP-0004-T04
status: todo
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.

id: GH-WP-0004-T05
status: todo
priority: low
state_hub_task_id: "8dd32a14-35d9-55c3-adfa-d9c728b550b1"

T06 — Ask informed-decision whether it should become a §4 catalog 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.

id: GH-WP-0004-T06
status: todo
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.

id: GH-WP-0004-T07
status: wait
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.

id: GH-WP-0004-T08
status: wait
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.

id: GH-WP-0004-T09
status: progress
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.

id: GH-WP-0004-T10
status: wait
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.

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, net-kingdom has flipped v0.8 to accepted, and T11's post-flip re-point is done.