Userinterface for executive decisions modeled as a sign and return book.

Find a file

tegwick 7ae67b2f4e Promote INFD-WP-0001 to active with a review note C-23 flagged lifecycle drift: the workplan was still 'proposed' while T02 sat at 'progress'. ADR-007 correctly refuses to auto-promote, so this is a deliberate promotion rather than a status the tool inferred. The plan is genuinely being worked and the review it was pending has happened: against approval-engine's INTENT/SCOPE/layer.yaml/WP-0002 and its keycape service registrations, the accepted security layer model v0.7 and companion, the repo-classification and project-repository-flavor standards, and the schema, state-transition tables and vectors in history/. Also corrected the body text, which claimed T03-T05 would all be rewritten if the ruling differs. That was too broad: only T05 and T07 depend on the catalog row. T03, T04 and T06 describe what the surface must do and what the evidence must contain, and neither changes with layer placement. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V3W1dQG7GFFM9d94jFx7iR Assistant: claude-code Assistant-Model: opus Assistant-Process: 1565372@bnt-lap001 Assistant-Session: 16bb2f25-b34c-49ef-8e94-5fec3567a568		2026-09-09 14:12:52 +02:00
docs	Add PRD and Use Case Catalog; file the gate-house request (T02-T04)	2026-09-09 14:11:36 +02:00
history/20260909-initial-exploration	Establish INTENT, Stage 1 GOAL, and founding workplan	2026-09-09 10:47:36 +02:00
intakes	Add PRD and Use Case Catalog; file the gate-house request (T02-T04)	2026-09-09 14:11:36 +02:00
workplans	Promote INFD-WP-0001 to active with a review note	2026-09-09 14:12:52 +02:00
.custodian-brief.md	chore(consistency): sync task status from DB [auto]	2026-09-09 14:12:01 +02:00
.repo-classification.yaml	Use in-vocabulary capability tags	2026-09-09 12:40:50 +02:00
AGENTS.md	Correct repo flavor to product; add SCOPE, AGENTS, classification	2026-09-09 12:38:41 +02:00
GOAL.md	Correct repo flavor to product; add SCOPE, AGENTS, classification	2026-09-09 12:38:41 +02:00
INTENT.md	Establish INTENT, Stage 1 GOAL, and founding workplan	2026-09-09 10:47:36 +02:00
README.md	Establish INTENT, Stage 1 GOAL, and founding workplan	2026-09-09 10:47:36 +02:00
SCOPE.md	Correct repo flavor to product; add SCOPE, AGENTS, classification	2026-09-09 12:38:41 +02:00
WORK-RECORDS.md	Promote INFD-WP-0001 to active with a review note	2026-09-09 14:12:52 +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).