tegwick
def0af2ce7
access-engine's boundaries review (FLEX-WP-0030, B1 corrected 2026-09-21) and the custodian's estate-wide sweep put six §11 interpretation questions here. All six are questions about what §11 means, and gate-house authors §11. GH-DEC-2026-017 — the layer declaration. INTENT.md governs and a sidecar is a derived artifact that must agree; a disagreement between the two forms is a finding in its own right and is reported rather than resolved away. The §3 vocabulary is case-insensitive for comparison and closed, and it has FOUR tokens: access-engine's validator omits Taxonomy, so railiance-master is conforming and the validator carries the defect. informed-decision's `surface` is not a layer; its own file already reasons to Staff. Both off-vocabulary repositories are outside §4 and §11 does not grade them. A declaration carries no standard version — and that field is the reference form's, not one repository's habit. gate-house declares Staff in INTENT.md frontmatter in this commit; the prose line was never a declaration under the paragraph this repository wrote. GH-DEC-2026-018 — access-engine is a source of evidence for the decision record, against its own interest and as it asked. Custody is never source: collapse them and §9.6 is incoherent. It owes a declaration, has none, and is non-conforming on §11 today; the right register is a declared gap with a date. The class inventory stays access-engine's to publish — §11's prohibition on inferring class binds a ruling as hard as a runner. Under it, §11 names a §4 property §4 does not carry, which is the finding under the finding, and the clause is gate-house's own A2 from twelve days ago. GH-DEC-2026-019 — the v0.8 acceptance flip stays held and these join the existing hold rather than a follow-on amendment. The round closed by finding that every substantive finding against v0.8 was a correct rule satisfiable without doing what it requires; §11 is now that failure pointed at §11. Bounded by three stated closing conditions. v0.7 stays accepted and in force, so the hold costs documentation currency and nothing else — stated as the reason it is affordable, not as an argument that holds are free. A candidate property is recorded and deliberately not numbered A-18: a conformance check each repository runs only against its own files cannot establish an estate property. One instance, and no repository bearing a cost under it has argued it yet. Amendments A9–A13 drafted; GH-IN-0003 and GH-WP-0004 carry the round. 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
4.4 KiB
| id | type | title | domain | repo | status | flavor | origin | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
§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
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
T03 — A11: INTENT.md governs, the sidecar is derived, a run states its scope
id: GH-WP-0004-T03
status: todo
priority: high
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.
id: GH-WP-0004-T04
status: todo
priority: medium
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
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.
id: GH-WP-0004-T06
status: todo
priority: medium
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
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
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.
id: GH-WP-0004-T09
status: progress
priority: high
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
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.