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

Find a file

tegwick 309bea463e Correct repo flavor to product; add SCOPE, AGENTS, classification fix-consistency surfaced that GOAL.md's `repo_flavor: project` was wrong. project-repository-flavor_v0.1.md reserves the prj- flavor for bounded cross-repo coordination efforts and says durable products use INTENT.md and an ordinary category. informed-decision is a durable product, so the C-35 "prj- flavor forbids shipping both INTENT.md and GOAL.md" contradiction was self-inflicted rather than a real conflict. - .repo-classification.yaml: category product, domain infotech. - GOAL.md: drop repo_flavor/project_status, add a flavor note explaining that GOAL.md is retained as the stage statement alongside a stable INTENT.md. - SCOPE.md: honestly empty — states that nothing is implemented and that INFD-WP-0001-T06 rewrites it after the gate-house ruling and the specs. - AGENTS.md: shared State Hub / session / workplan boilerplate, plus the hard rules for this repository — never decide, never own approval state, never invent identity, never let awareness enter view_hash, never let an agent bind, never fork the schema, fail closed. - INFD-WP-0001: T01 records both corrections; T06 now rewrites SCOPE.md. 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 12:38:41 +02:00
history/20260909-initial-exploration	Establish INTENT, Stage 1 GOAL, and founding workplan	2026-09-09 10:47:36 +02:00
workplans	Correct repo flavor to product; add SCOPE, AGENTS, classification	2026-09-09 12:38:41 +02:00
.custodian-brief.md	chore(consistency): sync task status from DB [auto]	2026-09-09 12:36:36 +02:00
.repo-classification.yaml	Correct repo flavor to product; add SCOPE, AGENTS, classification	2026-09-09 12:38:41 +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	Correct repo flavor to product; add SCOPE, AGENTS, classification	2026-09-09 12:38:41 +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).