What it is
DPS captures why a decision was made by binding events, inputs, rejected alternatives, authority, policy, jurisdiction, and time into immutable provenance.
DPS / Extended Systems
Decision Provenance System
Decision provenance and lineage preservation.
DPS captures why a decision was made by binding events, inputs, rejected alternatives, authority, policy, jurisdiction, and time into immutable provenance.
What problem it solves
Decisions are often remembered as narratives rather than preserved as provable lineage, especially once scrutiny arrives after the fact.
What it does
- Captures and canonicalizes decision material into deterministic decision objects and provenance records.
- Seals negative lineage such as rejected alternatives, excluded inputs, and refusal to decide.
- Preserves decision absence when defensible provenance does not exist.
What it does not do
- It does not execute decisions, judge correctness, infer intent, or summarize rationale.
- It does not act as decision support, analytics, or a justification engine.
- It does not contaminate the Truth Stack; it depends on it asymmetrically.
Who it is for
- Institutions that need why a decision was made to remain provable, challengeable, or provably broken.
- Programs where silent non-decisions are as dangerous as bad decisions.
Where it fits
DPS sits above VEF and the Truth Stack, and feeds TAE, oversight, and execution gating without owning custody.
Typical deployment context
Used where lineage, rejected options, and provenance completeness matter more than interpretive reporting.
Primary source docs
- Architecturedps/docs/09_architecture.md
- Threat modeldps/docs/01_threat_model.md