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

Define headless decision lifecycle product and delivery plan

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
tegwick 2026-10-04 17:33:43 +02:00
parent 5dd68eb8c1
commit 871f5e05e8
9 changed files with 381 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

33
INTENT.md
View file

@ -36,20 +36,43 @@ companion: net-kingdom/SECURITY-COMPANION.md
## Purpose
> **informed-decision owns the surface on which a human is shown a decision and
> binds their identity to it — and owns the evidence that the presentation
> actually happened.**
> **informed-decision provides the decision lifecycle service for agents and
> humans: research, retrieve, prepare, evaluate, register, publish, comment on,
> refine, and accept decisions. A headless foundation owns the memo lifecycle
> and evidence; the UI at `decisions.coulomb.social` uses that foundation.
> Humans alone perform binding dispositions.**
It answers one question, totally and decidably:
Its binding evidence answers the question:
> **What was this person shown, in what role, at the moment they bound
> themselves to this act — and can that be proven afterwards?**
Nothing else. It does not decide whether the act is permitted (`access-engine`),
Evaluation means assessing evidence, alternatives, consequences and recommendations;
it does not mean issuing an authorization verdict. This service does not decide
whether the act is permitted (`access-engine`),
does not own the approval object (`approval-engine`), does not author the
doctrine that requires an approval (`gate-house`), does not authenticate the
person (`key-cape`), and does not archive the trail (`audit-core`).
## Product direction — 2026-10-04
Decisions and their revisions are runtime data. Creating, registering, publishing,
commenting on, refining or accepting a decision within an admitted class must
require no image build, infrastructure release, policy redeployment, ConfigMap
swap or manual store load. Platform and policy changes can still require a
release; an ordinary new decision cannot.
The headless service provides the same lifecycle rules to agent clients and the
human UI. UI code owns rendering and interaction; it does not own a second
lifecycle or write the store directly. Research and evaluation records retain
sources, authorship and uncertainty. Publication has an explicit audience and
does not imply acceptance or anonymous access. Acceptance identifies an exact
revision and its presentation evidence.
The delivery contract is `docs/specs/DecisionLifecycleService.md`, tracked by
`INFD-WP-0007`, building on the intake in `INFD-WP-0005`. This direction extends
the first approver slice; it does not claim those capabilities are deployed.
## Why This Exists
Every layer of the NetKingdom estate has an owner except the one a human