Decision Evidence Ledger v1
data/build-020-engine-v1.jsonEight linked record classes, disclosed evidence gaps, append-only correction, and local export.
RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
BUILD 020
Decision Evidence Ledger
A decision is accountable only when its actor, authority, time, evidence, alternatives, acknowledgement, result, and correction history remain linked without silently replacing earlier records.
QUESTIONWhy was this decision made, and can its evidence and result be reconstructed?
STRUCTURED PUBLIC BUILD ARCHIVE
Research, creation, decisions, audits and plans are publicly structured without claiming that every release gate is complete.
This page exists so the durable record does not depend on conversation history. Research, decisions, generated artifacts, audits, limitations, media metadata, plans and canonical source paths are retained here as part of the build itself. A listed repository path proves that an implementation record was retained; it does not independently support a real-world factual claim.
0 of 5 listed retained paths have a public reader link on this archive page. Unlinked paths remain named for traceability but are not represented as publicly inspectable evidence.
What informed the build
W3C PROV-O
Grounds entities, activities, agents, attribution, derivation, and temporal provenance.
NIST SP 800-53 Rev. 5
Grounds audit-event content, timestamps, review, protection, and retention controls.
What exists because we built it
020-A Decision Evidence Ledger
Reconstructs a synthetic decision, exposes missing evidence, appends corrections, and exports locally.
020-B Open the Decision
Progressively opens one outcome into its actor, authority, evidence, alternatives, result, and correction chain.
Decision Record and Evidence Chain v1
Reusable provenance primitives for later procurement, incident, change, governance, and research builds.
Why it works this way
Canonical versus implementation copy is explicit
Title, job, B-web, and lineage are canonical; the displayed question and thesis are derived implementation copy.
Corrections do not erase history
A correction appends a reasoned superseding record and retains the original.
Provenance is not proof
A complete chain does not itself establish truth, causation, legality, authority validity, or substantive correctness.
Builds 001, 010, and 019 are concrete dependencies
The ledger inherits review authority, explicit entities/relationships, and acknowledgement/escalation records.
How the work was checked
Machine-readable archive
data/build-020-archive-v1.jsonRoutes, lineage, privacy, deferred gates, and lifecycle.
RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Privacy/support
data/build-020-privacy-support-v1.jsonSynthetic client-local fixture and provenance boundary.
RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Freshness/performance
data/build-020-freshness-performance-v1.jsonPrimary provenance and audit-control sources with deterministic offline operation.
RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Browser fixtures
tests/build020.spec.tsComplete chain, evidence gap, append correction, export, 320px, and paired visual coverage.
RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
What this build intentionally leaves forward
Release path
Complete static gates, Vercel deployment, authenticated browser and physical-device accessibility review; certify media independently.
Future consumers
021, 023, 026, 029, 032, 033, 034, 037, 038, 039, 041, 044, 057, 058, 060, 061, 069, 071, 084, 088, 092, 093, 094 and 100 consume cap:020.
Take the social artifact with you
B-LINKEDIN / CANONICAL FILM
720×900 · 4:5 MP4 · 24 fps · silent-first
CURRENT VERIFIED MEDIA / 30-second film · 348.8 KB
FINAL PROPOSITION / AN ACCOUNTABLE DECISION REMAINS RECONSTRUCTABLE AFTER THE MOMENT HAS PASSED.
SHA-256 889456c488c0e68e26d17990c6f6c67291d830e62a394361ad04de47e4c679ceReproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.
The repository files that preserve the implementation record
apps/web/app/100-builds/020/a/DecisionEvidenceLedger.tsxapps/web/app/100-builds/020/b/DecisionChain.tsxdata/build-020-engine-v1.jsondata/build-020-archive-v1.jsondocs/builds/020/SPEC.mddocs/builds/020/ARCHIVE.mdtests/build020.spec.tsThese paths preserve the implementation record. Only items with an explicit public reader link are publicly inspectable here. A file path, working interface or internal engine is not independent support for a real-world claim; synthetic propositions and design reasoning remain labeled within the retained record.