Decision-readiness engine + evidence boundary
data/build-008-engine-v1.jsonMetric completeness, action-state gates, inherited human-control scoring, status logic, provenance, and non-claims.
BUILD 008
Decision-Ready Dashboard Standard
A dashboard becomes decision-ready only when relevant evidence is connected to a named decision, accountable owner, authorized action, timing, escalation, and an observable next state—with a human able to review caveats and resolve conflicts.
QUESTIONWhen does a dashboard become a decision path?
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.
7 of 7 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
Complete Build 008 archive
docs/builds/008/ARCHIVE.mdPurpose, retained research, Build 001 inheritance, decisions, rejected approaches, QA state, and forward lineage.
Build 008 specification
docs/builds/008/SPEC.mdPurpose, inputs, assessment contract, acceptance criteria, and evidence requirements.
CDC dashboard guidance
Dashboards are appropriate when related visualizations and common filtering serve a combined purpose; not every dataset needs one.
W3C WCAG 2.2 distinguishable guidance
Status and controls must remain perceivable through contrast, reflow, resizing, and cues beyond color.
What exists because we built it
008-A Decision-Ready Dashboard Standard
Name a decision, justify every metric, complete the accountable action state, inspect gaps, and export a local record.
008-B Data Is Not a Decision
Interactive chart-wall, signal, decision-ready, and conflict states that expose the human control node.
Decision Readiness Rubric v1
Completeness checks for decision-useful metrics and eight explicit action-state gates.
Action-State Component v1
Decision → owner → action → next state, with trigger, deadline, authority, and escalation.
Why it works this way
Start with the decision
A metric must state how it can change the named decision; otherwise it remains information only.
Completeness is not correctness
The rubric cannot prove source quality, causality, organizational authority, compliance, or decision quality.
Build 001 is concretely inherited
The engine imports humanReviewScore and humanReviewGrade and exposes the inherited result.
Conflict requires escalation
Competing obligations are surfaced for accountable human resolution rather than hidden behind a composite score.
Status is not color-only
Every B state is expressed in text, structure, control state, and copy as well as visual treatment.
How the work was checked
008 privacy/support record
data/build-008-privacy-support-v1.jsonLocal-state privacy, no persistence, export, and support boundary.
008 freshness/performance record
data/build-008-freshness-performance-v1.jsonNo-network/no-model core value, dependency, freshness, and resilience record.
008 LinkedIn production record
docs/builds/008-linkedin-production.mdDeterministic 4:5 film specification, checksum, reproduction, and verification boundary.
008 adversarial browser fixtures
tests/build008.spec.tsReady, incomplete, empty, metric lifecycle, export, 320px, scenario state, human control, and conflict behavior.
What this build intentionally leaves forward
Release path
Complete Chromium/WebKit, accessibility, 320px, reduced-motion, archive, media, preview, and exact-head certification.
Future consumer
Canonical Build 071 explicitly inherits cap:008.
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 · 330.2 KB
FINAL PROPOSITION / DATA BECOMES USEFUL WHEN SOMEONE CAN DECIDE AND ACT.
SHA-256 2958ede0116dfaf6b331c1ad91149717bbc42e4784ea54129fc74c8533410b2dReproducible 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/008/a/DecisionDashboardLab.tsxapps/web/app/100-builds/008/b/DecisionPathField.tsxpackages/release/src/decision-engines.tsdata/build-008-engine-v1.jsondocs/builds/008/SPEC.mddocs/builds/008/ARCHIVE.mddocs/builds/008-linkedin-production.mddata/build-008-privacy-support-v1.jsondata/build-008-freshness-performance-v1.jsontests/build008.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.