data/build-021-engine-v1.jsonFour disclosed verification paths and three non-binary verdicts over synthetic claims.
A vendor promise becomes decision-ready only when the exact entity, proposition, evidence, scope, consequence, control, commitment, remedy, and correction path are explicit.
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.
data/build-021-engine-v1.jsonFour disclosed verification paths and three non-binary verdicts over synthetic claims.
Grounds risk, context, measurement, governance, and documentation.
Breaks synthetic claims into evidence, scope, independent verification, and enforceable commitment.
Progressively reveals the verification path beneath one promise.
Reusable vendor-claim evidence and gap primitives for Build 025.
Title, job, B-web, and lineage are canonical; question, thesis, fixtures, thresholds, and interface language are derived.
The x-ray makes identity resolution, consequence controls, and reconstructable evidence visible.
A closed claim does not endorse the vendor, product, or use outside the stated context.
data/build-021-archive-v1.jsonRoutes, lineage, retention, and deferred gates.
data/build-021-privacy-support-v1.jsonSynthetic client-local fixture and procurement boundary.
data/build-021-freshness-performance-v1.jsonPrimary NIST sources and deterministic offline operation.
tests/build021.spec.tsVerdicts, identity separation, export, 320px, and paired visual coverage.
Complete static gates and Vercel deployment; keep authenticated browser, physical-device accessibility, GitHub-hosted CI, and media certification independent.
025 consumes cap:021.
CURRENT VERIFIED MEDIA / 30-second film · 348.2 KB
FINAL PROPOSITION / BUY THE EVIDENCE—NOT THE ADJECTIVE.
SHA-256 2322b33db6e1eb06a086fdfa0ea86ba32448fa27fa31640a4ee6ffa627cd88b8Reproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.apps/web/app/100-builds/021/a/VendorClaimLab.tsxapps/web/app/100-builds/021/b/ClaimXRay.tsxdata/build-021-engine-v1.jsondata/build-021-archive-v1.jsondocs/builds/021/SPEC.mddocs/builds/021/ARCHIVE.mdtests/build021.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.