coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Correct the layer-declaration record: Taxonomy is a section 3 layer.

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-09-21 02:13:09 +02:00
parent 736a740286
commit fcc86bda0e
1 changed files with 39 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

49
docs/assessments/2026-09-21-layer-declaration-boundaries.md
View file

@ -50,14 +50,33 @@ The review surveyed the twelve counterparts flex-auth has boundaries with. An
estate-wide sweep of every repository carrying a declaration finds fourteen, and
the three it did not cover change two of its conclusions.
**Two repositories declare values outside the §3 vocabulary.**
`informed-decision` declares `surface` and `railiance-master` declares
`Taxonomy`, in both files. flex-auth's validator admits only
`{Staff, Engine, Tooling}`, so these fail it on the value rather than on casing
or precedence — a third non-conformance class, and the only one where the
declared layer is not a layer the model defines. Whether §3's vocabulary is
closed, or these name a real tier the model has not enumerated, is a question
for the same ruling that settles B1.
**One repository declares a value outside the §3 vocabulary — not two.**
`informed-decision` declares `surface`, which appears nowhere in the model as a
layer. `railiance-master` declares `Taxonomy`, and **`Taxonomy` is §3's first
enumerated layer**, defined in §3.1, carried in §4's catalog, mapped in §7 and
given its own §17. The custodian's first reading of this finding was wrong: it
took flex-auth's validator set `{Staff, Engine, Tooling}` for the §3 vocabulary.
§3 enumerates four layers — Taxonomy, Tooling, Engines, Staff. The correction is
railiance-master's, with the citations, and it is recorded here rather than
quietly amended because the first version was circulated to gate-house.
What remains of the finding is sharper and is aimed at the validator and the
standard, not at the declaring repositories:
- **flex-auth's validator omits §3.1 and misspells §3.3.** It admits `Engine`
where §3's table writes `Engines`, and omits `Taxonomy` altogether. Its set
looks built from §4's role-typed catalog rows rather than from §3.
- **§3 and §4 disagree inside the standard.** §3's table says `Engines`; §4's
catalog types eight rows `Engine`. A conformance run built from §3 and one
built from §4 disagree about every engine repository in the estate. That is
the same defect as B1 — two readings of one standard, both faithful — one
level further in, and B1's precedence ruling does not reach it.
- **`railiance-master`'s casing matches §3's table exactly.** Against the
standard's own spelling, the nine lower-casing `layer.yaml` files are the
divergent ones, which bears on whether case sensitivity is even the question.
`informed-decision`'s `surface` is a genuinely separate case and does not
behave like `railiance-master`'s. The two should not be ruled on together.
**The "two generators, two conventions" reading does not hold estate-wide.**
Nine of nine is true of the repositories flex-auth surveyed, but
@ -78,12 +97,12 @@ split for the same reason.
|---|---|---|
| 1 | Which §11 form governs when both are present | gate-house |
| 2 | Is the §3 vocabulary case-sensitive | gate-house |
| 3 | Is §3's vocabulary closed — `surface`, `Taxonomy` | gate-house |
| 3 | Is §3's vocabulary closed — `surface` only; `Taxonomy` is §3.1 | gate-house |
| 4 | gate-house's own layer declaration (B2) | gate-house |
| 5 | Is flex-auth a §4 source of evidence (B3) | gate-house |
| 6 | May a declaration carry a standard version (B4) | gate-house |
| 7 | Which side of the B3 line audit-core holds | audit-core |
| 8 | What `CheckRequest.tenant` denotes on the write API | tenant-engine |
| 8 | What `CheckRequest.tenant` denotes on the write API — ANSWERED, TEN-DEC-2026-002 | tenant-engine |
| 9 | Layer declarations for key-cape, ops-mason, net-kingdom (B2) | each owner |
gate-house holds six of the nine, including the ruling that decides whether
@ -119,3 +138,13 @@ than in a follow-on amendment.
None of this is the custodian's to rule. §11 is net-kingdom canon authored by
gate-house, and the custodian's contribution is the estate-wide survey and the
observation that the questions concentrate in one repository.
## Correction, 2026-09-21
The first version of this record claimed two repositories declared values
outside §3's vocabulary. `Taxonomy` is in §3. The error was the custodian's and
was made in the same shape as the one flex-auth had just corrected: a survey run
against an artifact that stands in for the standard — there, a shell pipeline;
here, another repository's validator — and published without reading §3 itself.
A tenth question follows from the correction: whether §3's `Engines` or §4's
`Engine` governs a declaration.