coulomb/informed-decision
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Narrow INFD-IN-0006 to surface alone after railiance-master's correction

Browse source 
The custodian's record was corrected on 2026-09-21 while this request was being
written. railiance-master had already established — with fuller citations than
this repository had — that flex-auth's validator set {Staff, Engine, Tooling} is
not §3's enumeration: §3 has four rows and `Taxonomy` is the first, defined in
§3.1, catalogued in §4, mapped in §7 and given its own §17. It added the sharper
finding this repository had not reached: §3's table writes `Engines` while §4
types eight rows `Engine`, so two faithful conformance runs disagree about every
engine in the estate.

This repository reached the first half independently and before seeing the
correction, and now records it rather than re-arguing it. The consequence is
what matters: `surface` is the only surveyed value outside §3 itself, and the
only one that needs a ruling on whether the vocabulary is closed. The two cases
do not behave alike and should not be ruled on together — which is what the
corrected record says, and this repository agrees.

One point carries over into the closed outcome: if §3's vocabulary is ruled
closed, the closed set should be written out as declaration values rather than
inferred from table row labels. `Engines`/`Engine` is what happens otherwise,
and it is B1's shape one level further in.

Position unchanged; the declared value remains unchanged pending the ruling.

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
This commit is contained in:
tegwick 2026-09-21 02:14:00 +02:00
parent 13ee949982
commit d0d0bad66d
3 changed files with 35 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

18
intakes/intakes.md
View file

@ -304,6 +304,7 @@ description: >-
prove the full browser path, not just redirect parameter forwarding.
T03's three human approvals and key check subsequently completed; this is
ongoing authentication reliability work, not an outstanding T03 execution.
state_hub_intake_id: "01a0c14e-f965-788f-8efb-4424f1f1ad08"
```
@ -358,11 +359,16 @@ description: >-
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:
Scope narrowed the same day: railiance-master had already established, with
fuller citations, that flex-auth's validator set is not section 3's enumeration
— section 3 has four rows and `Taxonomy` is the first — and the custodian's
record was corrected to say so, adding that section 3 writes `Engines` while
section 4 types eight rows `Engine`. This repository reached the first half
independently and does not re-argue it. The consequence is that `surface` is
the only surveyed value outside section 3 itself and the only one needing this
ruling; the two cases should not be ruled on together. One point carries over:
if the set is ruled closed it should be written out as declaration values
rather than inferred from table row labels. Full request:
docs/gate-house-decision-request-layer-vocabulary.md.
state_hub_intake_id: "01a0c14f-17b6-72fb-8951-8c933bd05d6b"
```