coulomb/informed-decision
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Userinterface for executive decisions modeled as a sign and return book.
70 commits 1 branch 0 tags 2.1 MiB
Find a file
tegwick 13ee949982 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
2026-09-21 02:11:59 +02:00
deploy Restore login compatibility with deployed Authelia 4.38 2026-09-16 01:51:38 +02:00
docs Raise INFD-IN-0006: is §3's layer vocabulary closed, and what is surface? 2026-09-21 02:11:59 +02:00
history/20260909-initial-exploration Establish INTENT, Stage 1 GOAL, and founding workplan 2026-09-09 10:47:36 +02:00
informed_decision Restore login compatibility with deployed Authelia 4.38 2026-09-16 01:51:38 +02:00
intakes Raise INFD-IN-0006: is §3's layer vocabulary closed, and what is surface? 2026-09-21 02:11:59 +02:00
schemas Promote schema and canonicalizer out of history; add EvidenceModel (T06) 2026-09-09 14:16:28 +02:00
tests Restore login compatibility with deployed Authelia 4.38 2026-09-16 01:51:38 +02:00
tools Publish renewed T03 memo versions with the admitted review policy 2026-09-16 01:08:56 +02:00
workplans Cut review over to the sitting PDP and load seven memos. 2026-09-15 23:35:35 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-14 17:09:09 +02:00
.dockerignore Package protected review runtime and prepare deployment admission 2026-09-11 01:21:37 +02:00
.gitignore Package protected review runtime and prepare deployment admission 2026-09-11 01:21:37 +02:00
.repo-classification.yaml Use in-vocabulary capability tags 2026-09-09 12:40:50 +02:00
AGENTS.md Raise INFD-IN-0006: is §3's layer vocabulary closed, and what is surface? 2026-09-21 02:11:59 +02:00
Containerfile Package protected review runtime and prepare deployment admission 2026-09-11 01:21:37 +02:00
Containerfile.memo-input Require fresh KeyCape authentication for decision review sign-in 2026-09-16 01:35:02 +02:00
Containerfile.memo-input.dockerignore Require fresh KeyCape authentication for decision review sign-in 2026-09-16 01:35:02 +02:00
GOAL.md Declare the layer per GH-DEC-2026-012; close T02 2026-09-09 22:25:35 +02:00
INTENT.md Raise INFD-IN-0006: is §3's layer vocabulary closed, and what is surface? 2026-09-21 02:11:59 +02:00
layer.yaml Raise INFD-IN-0006: is §3's layer vocabulary closed, and what is surface? 2026-09-21 02:11:59 +02:00
Makefile Package protected review runtime and prepare deployment admission 2026-09-11 01:21:37 +02:00
pep-stance.yaml Declare the layer per GH-DEC-2026-012; close T02 2026-09-09 22:25:35 +02:00
pyproject.toml Package protected review runtime and prepare deployment admission 2026-09-11 01:21:37 +02:00
README.md Establish INTENT, Stage 1 GOAL, and founding workplan 2026-09-09 10:47:36 +02:00
requirements.lock Package protected review runtime and prepare deployment admission 2026-09-11 01:21:37 +02:00
SCOPE.md Record native sender acceptance and retained audit readback gate 2026-09-11 14:23:07 +02:00
uv.lock Deploy verified-group T03 review surface and packet preparation 2026-09-14 02:47:31 +02:00
WORK-RECORDS.md Index INFD-WP-0002 T01–T02 after fix-consistency writeback. 2026-09-14 17:09:10 +02:00

README.md

informed-decision

User interface for executive decisions, modelled as a sign-and-return book — the German Umlaufmappe / Zeichnungsbuch, made cryptographic.

A Decision Memo carries a question, the context needed to answer it, the requested act, and a binding between identity, what was shown, and what was bound. The promise is not "the file was signed" but "this person, in this role, was shown this view, and bound this act."

One object model from a ten-second login (L0) to a multi-party instrument (L5).

Where to start

File What it is
INTENT.md Why this repository exists and what it must never become
GOAL.md The current stage, its invariants, and its definition of done
workplans/ Current work
history/20260909-initial-exploration/ Founding exploration — schema, state transitions, canonicalization, vectors

Stage 1

Own the browser-facing approver UI that approval-engine deliberately does not contain, and answer in writing who owns it. approval-engine is a bearer-token resource server with no browser client; key-cape (KEY-WP-0013-T02) is waiting on a client_id and callback URI that no component has claimed. This repository claims them.

See GOAL.md.

Boundaries

This repository renders questions and records answers. It does not decide (access-engine), does not own the approval object (approval-engine), does not author approval doctrine (gate-house), does not authenticate anyone (key-cape), and does not archive the trail (audit-core).