Rule the six §11 declaration questions, and hold the v0.8 flip on them

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

intakes/intakes.md

@@ -163,3 +163,54 @@ created: '2026-09-05T23:28:11.977565Z'
 updated: '2026-09-05T23:28:11.977565Z'
 state_hub_intake_id: "01a08762-ab47-7163-8eeb-92c3cb909db3"
 ```
+
+## GH-IN-0003 — Six §11 interpretation questions from the access-engine boundaries review
+
+```yaml
+id: GH-IN-0003
+kind: intake
+title: Six section 11 interpretation questions from the access-engine boundaries review
+status: closed
+origin: cross-repo
+origin_ref: access-engine FLEX-WP-0030 docs/conformance/boundaries-review.md (published
+  2026-09-20, B1 corrected 2026-09-21); the-custodian docs/assessments/2026-09-21-layer-declaration-boundaries.md
+priority: high
+owner: gate-house
+requested_by: access-engine, the-custodian
+lane: red
+description: 'access-engine surveyed twelve security-relevant counterparts against section
+  11 and published five findings. the-custodian swept the whole estate, found fourteen
+  declarations rather than ten, and recorded that six of the nine resulting open questions
+  are gate-house''s because every one of them asks what section 11 means and gate-house
+  authors section 11.
+
+
+  The six: (1) which section 11 declaration form governs when a repository carries both an
+  INTENT.md layer key and a layer.yaml, and they disagree — nine repositories do, in all
+  nine; (2) whether the section 3 vocabulary is case-sensitive; (3) whether the section 3
+  vocabulary is closed, given informed-decision declares surface and railiance-master
+  declares Taxonomy; (4) gate-house''s own missing layer declaration (B2), alongside
+  key-cape, ops-mason and net-kingdom; (5) whether access-engine is a section 4 source of
+  evidence for the decision record (B3), held open as its declared gap G2 with audit-core
+  holding the other half; (6) whether a layer declaration may carry a standard version (B4).
+
+
+  Also carried: the custodian''s reading, offered and not pressed, that the v0.8 acceptance
+  flip should not proceed while section 11''s own mechanical check is ambiguous.
+
+
+  Declarations re-verified here from the repositories'' own files before ruling, rather than
+  taken from either report. Resolved as GH-DEC-2026-017 (declaration form, vocabulary,
+  version, and gate-house''s own declaration), GH-DEC-2026-018 (source of evidence), and
+  GH-DEC-2026-019 (the v0.8 hold). Amendments A9-A13 drafted at
+  docs/amendments/v0.8-section-11-declaration-amendments.md and carried by GH-WP-0004.
+
+
+  B5 (canon names access-engine; the repository still answers to flex-auth) is not one of
+  the six and is not ruled here — it is a coordinate note against section 4, already
+  sequenced under FLEX-WP-0020, and is carried as GH-WP-0004-T05.'
+created: '2026-09-21T00:00:00.000000Z'
+updated: '2026-09-21T00:00:00.000000Z'
+outcome: ruled
+state_hub_intake_id: ""
+```