Claim-to-source evidence map
data/build-001-evidence-v1.jsonPrimary-source basis for the dimensions used in the framework, including source-vs-heuristic distinctions and freshness notes.
BUILD 001
Human Review Design Framework
Human presence is not the same thing as meaningful human review. Timing, evidence, authority, escalation, records, and the ability to change or stop an outcome have to be designed separately.
QUESTIONWhen is a human actually a control?
CERTIFIED PUBLIC BUILD ARCHIVE
The complete structured public archive is certified for this build.
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.
6 of 6 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
NIST AI RMF 1.0
Mapped into the evidence layer as a governance source family rather than treated as proof of the product score.
EU AI Act Articles 13–14
Used for transparency/human-oversight source grounding where relevant.
UK ICO AI audit toolkit — human review
Used as a primary governance source family for meaningful human review concepts.
001 specification
docs/builds/001/SPEC.mdOriginal build purpose, scope, use case, system behavior, audience range, and constraints.
What exists because we built it
001-A working tool
Quick/deep diagnostic that turns plain-language workflow answers into prioritized human-review design findings.
001-B interactive visual
Motion/interaction reveal that decomposes “human in the loop” into the hidden architecture of review.
Making page
Visible build-development history and design changes.
Method page
Reusable method and conceptual decomposition.
Public record
Making, method, evidence, and limits in visitor-facing form.
Shared reusable primitives
Form Engine v1, Conditional Logic v1, Results Renderer v1, Visual Reveal Primitive v1, and Exhibition Room Shell v1 are recorded in the infrastructure manifest.
Why it works this way
Broad comprehension range
The interface was rewritten so an early-secondary reader can begin while a domain/technical reader can still inspect deeper control logic.
Score is heuristic
Composite scoring/thresholds are explicitly product heuristics, not legal or compliance determinations.
Interactive B is a separate artifact
The explanatory visual became a first-class interactive master rather than a static slideshow attached to A.
How the work was checked
001–003 certification ledger
docs/builds/001-003-certification-ledger.mdAutomated release evidence, browser matrix, manual-device distinctions, and exact release history.
001 release record
docs/builds/001-release-record.mdRelease-state record for 001.
001–003 security review
docs/builds/001-003-security-review.mdShared privacy/security review for the first tranche.
001–003 acceptance + artifact + freshness/privacy records
data/build-001-003-acceptance-v1.jsonMachine-readable acceptance, artifact, resilience, and privacy/support ledgers.
What this build intentionally leaves forward
Standing reuse
001’s room shell and interaction primitives are intended to be inherited only when a later build has a concrete dependency—not merely thematic similarity.
Physical-device review remains distinct
Automated certification does not replace any separately required physical-device/manual accessibility review.
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 · 356.8 KB
FINAL PROPOSITION / A HUMAN IS A CONTROL ONLY IF THEY CAN CHANGE THE OUTCOME.
SHA-256 e2dc21463baadf51574ac06e47f75fb257101c8e38044b45201f29efdcaa2107Reproducible 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/001/a/page.tsxapps/web/app/100-builds/001/b/page.tsxapps/web/app/100-builds/001/evidence/page.tsxapps/web/app/100-builds/001/making/page.tsxapps/web/app/100-builds/001/method/page.tsxdata/build-001-evidence-v1.jsondocs/builds/001/SPEC.mddocs/builds/001-release-record.mddocs/builds/001-003-certification-ledger.mddocs/builds/001-003-linkedin-artifact-manifest.jsondocs/builds/001-003-linkedin-production-specs.mdThese 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.