Raise INFD-IN-0006: is §3's layer vocabulary closed, and what is surface?

The custodian's estate-wide sweep (2026-09-21), extending flex-auth's boundaries
review FLEX-WP-0030, found this repository declaring `layer: surface` against a
§3 vocabulary that does not enumerate it. flex-auth's validator admits only
{Staff, Engine, Tooling}, so this fails on the value rather than on casing or on
B1's precedence question. It was never raised here directly and it is not the
nine-repository defect: both our files say `surface`, in the same casing.

`surface` denotes the presentation-and-binding tier — the runtime a human
touches, where a decision rendered elsewhere is shown to a named person, that
person binds their identity to the act, and the evidence that the presentation
happened is produced. It was chosen by elimination on 2026-09-09 (f6376dd),
because GH-DEC-2026-012 R1 ruled us out of Engine and left the layer ours to
declare, and each remaining value is false of us: not Staff (deterministic by
construction, and holding state audit-core depends on at runtime, which §3.4
forbids Staff), not Tooling (we persist nothing another layer reads), not
Taxonomy (we are nothing but a runtime position). Faced with a false value that
satisfies a validator or the true word and a finding, the true word was written.

Position: `surface` names a real tier §3 does not enumerate. The sharpest form
is that a standing ruling plus a closed vocabulary leaves this repository no
conforming declaration available — the §9.1 defect applied to conformance that
§11 names against itself. But the ruling is gate-house's and we do not claim it
must go our way: if the vocabulary is ruled closed and a value named, both files
change the same day without argument. We ask only that such a ruling show how
§3's determinism cut reaches that value given GH-DEC-2026-012 R1, because the
next repository in this position will reason from it — and the tier a human
touches having no owner is exactly what produced approval-engine's unowned
inbox, key-cape's blocked client_id, and this repository.

Two observations offered: flex-auth's validator admits three values where §3
enumerates four, so railiance-master's `Taxonomy` fails the validator rather
than the standard and is separable without any ruling, leaving `surface` as the
only surveyed value outside §3 itself; and §3's row label is `Engines` while
declarations use `Engine`, which should be written out as declaration values if
the set is ruled closed.

The declared value is UNCHANGED on purpose. Changing it ahead of the ruling
would pre-empt gate-house and throw away the evidence of what was concluded.
layer.yaml, INTENT.md and AGENTS.md now say so in place, so the value is not
read as unexamined and no later agent silently "fixes" it. AGENTS.md's layer
section was also stale — it still said layer.yaml was unwritten.

28 layer conformance tests pass.

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

@@ -305,3 +305,64 @@ description: >-
   T03's three human approvals and key check subsequently completed; this is
   ongoing authentication reliability work, not an outstanding T03 execution.
 ```
+
+
+## INFD-IN-0006 — Is §3's layer vocabulary closed, and what is `surface`?
+
+```yaml
+id: INFD-IN-0006
+kind: intake
+title: Is section 3's layer vocabulary closed, and what is `surface`?
+status: open
+origin: coordination
+origin_ref: the-custodian/docs/assessments/2026-09-21-layer-declaration-boundaries.md
+priority: medium
+owner: gate-house
+repo: informed-decision
+lane: blue
+tags:
+- decision-request
+- cross-repo
+- conformance
+created: '2026-09-21'
+updated: '2026-09-21'
+description: >-
+  This repository declares `layer: surface` in both INTENT.md frontmatter and
+  layer.yaml. Section 3 of security-layer-model_v0.8.md enumerates four layers —
+  Taxonomy, Tooling, Engines, Staff — and `surface` is not among them;
+  flex-auth's conformance validator reads the vocabulary as closed and admits
+  only {Staff, Engine, Tooling}, so this repository fails it on the value rather
+  than on casing or on the B1 precedence question. Surfaced by the custodian's
+  estate-wide sweep extending flex-auth's boundaries review (FLEX-WP-0030); it
+  was never a finding raised against this repository directly. Two facts bound
+  it: this repository is internally consistent — both files say `surface` in the
+  same casing, so it is not part of the nine-repository B1 disagreement — and it
+  has no section 4 catalog row, having declared ahead of being catalogued.
+  `surface` denotes the presentation-and-binding tier: the runtime a human
+  touches, where a decision rendered elsewhere is shown to a named person, that
+  person's identity is bound to the act, and the evidence that the presentation
+  happened is produced. It was chosen by elimination on 2026-09-09 (f6376dd),
+  in this repository's own voice, because GH-DEC-2026-012 R1 ruled it out of
+  Engine and left the layer to it to declare, and because each remaining section
+  3 value is false of it — not Staff (deterministic by construction, and holding
+  state audit-core depends on at runtime, which section 3.4 forbids Staff), not
+  Tooling (persists nothing another layer reads), not Taxonomy (nothing but a
+  runtime position). POSITION: `surface` names a real tier section 3 does not
+  enumerate, the sharpest form being that a standing ruling plus a closed
+  vocabulary would leave this repository no conforming declaration available —
+  the section 9.1 defect applied to conformance that section 11 names. This
+  repository does not claim the ruling must go its way: if gate-house rules the
+  vocabulary closed and names which of the four values applies, both files
+  change the same day without argument, and it asks only that such a ruling show
+  how section 3's determinism cut reaches that value given GH-DEC-2026-012 R1,
+  because the next repository in this position will reason from it. The declared
+  value is deliberately UNCHANGED pending the ruling: changing it first would
+  pre-empt gate-house and destroy the evidence of what was actually concluded.
+  Also offered: flex-auth's validator admits three values where section 3
+  enumerates four, so railiance-master's `Taxonomy` fails the validator rather
+  than the standard and is a separable, ruling-free correction, leaving `surface`
+  as the only surveyed value outside section 3 itself; and section 3's row label
+  is `Engines` while declarations and the validator use `Engine`, which should be
+  written out as declaration values if the set is ruled closed. Full request:
+  docs/gate-house-decision-request-layer-vocabulary.md.
+```