2026-09-09 06:41:05 +00:00
|
|
|
# informed-decision
|
|
|
|
|
|
2026-10-04 17:33:43 +02:00
|
|
|
Decision lifecycle service for agents and humans: research, retrieve, prepare,
|
2026-10-05 00:21:06 +02:00
|
|
|
evaluate, register, publish, comment, refine and human acceptance. The deployed initial
|
2026-10-04 17:33:43 +02:00
|
|
|
architecture separates a headless foundation from the UI at
|
|
|
|
|
`decisions.coulomb.social`; new decisions are runtime data, requiring no
|
|
|
|
|
per-decision infrastructure rollout.
|
|
|
|
|
|
|
|
|
|
See the [product and architecture contract](docs/specs/DecisionLifecycleService.md)
|
|
|
|
|
and [delivery workplan](workplans/INFD-WP-0007-decision-lifecycle-service.md).
|
2026-10-05 00:21:06 +02:00
|
|
|
The initial production audience is live and human acceptance is confirmed.
|
|
|
|
|
[SCOPE.md](SCOPE.md) records the delivered boundary and remaining work.
|
Establish INTENT, Stage 1 GOAL, and founding workplan
Claim ownership of the browser-facing approver UI that approval-engine
deliberately does not contain. approval-engine's INTENT names an approvals
inbox under Non-Goals, and docs/keycape-service-registrations.md records that
the human approver client's client_id and callback URI "must come from its
owner once it exists" — leaving key-cape's KEY-WP-0013-T02 blocked on an
unassigned component.
- INTENT.md: Decision Memo concept, the binding/awareness split and the two
hashes, ownership and non-ownership against the named estate repositories,
and a provisional PEP-shaped layer placement flagged for a gate-house ruling
rather than asserted.
- GOAL.md: Stage 1 is the L3 approval approver surface — the narrowest real
consumer with a live blocking dependency — plus the written answer to who
owns the approver UI.
- workplans/INFD-WP-0001: founding documents, the gate-house layer/ownership
ruling, the four specs (PRD, UseCaseCatalog, ArchitectureBlueprint,
EvidenceModel), schema and canonicalizer promotion out of history/ with the
isolation vectors under test, the key-cape client registration, and a
walking skeleton that includes return and discuss.
history/ is preserved unmodified as provenance.
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 10:47:36 +02:00
|
|
|
|
|
|
|
|
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`).
|
2026-10-05 00:21:06 +02:00
|
|
|
|
|
|
|
|
## Production intake and historical fallback
|
|
|
|
|
|
|
|
|
|
For the admitted State Hub / decision-record audience, register, revise and
|
|
|
|
|
publish through the private lifecycle API, request review, then explicitly queue
|
|
|
|
|
the returned envelope in the State Hub dispatcher. The human reviews through
|
|
|
|
|
the existing protected browser path. See [the deployed release](deploy/lifecycle/README.md).
|
|
|
|
|
|
|
|
|
|
`tools/create_sitting_approvals.py` / `.sh`, `tools/attach_compact_bindings.py` and
|
|
|
|
|
`tools/load_sitting_memos.py` are historical compact-sitting fallback tools. They
|
|
|
|
|
are not the normal path for new admitted decisions. Their original attended
|
|
|
|
|
custody and approval requirements still apply; do not use them to bypass intake,
|
|
|
|
|
uncertain-create handling, policy checks or human binding. Historical batch
|
|
|
|
|
runbooks remain provenance, not the current intake workflow.
|