Skip to main content
← BUILD 021PROGRAM ARCHIVE
DURABLE BUILD ARCHIVE / STRUCTURED PUBLIC · CERTIFICATION OPEN

BUILD 021
AI Vendor Claim / Procurement X-Ray

A vendor promise becomes decision-ready only when the exact entity, proposition, evidence, scope, consequence, control, commitment, remedy, and correction path are explicit.

QUESTIONWhat would have to be true before this vendor claim could support a procurement decision?
STRUCTURED PUBLIC BUILD ARCHIVE

Research, creation, decisions, audits and plans are publicly structured without claiming that every release gate is complete.

DURABLE-RECORD RULE

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.

SOURCE-LINK AVAILABILITY

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.

01 / RESEARCH + EVIDENCE

What informed the build

Vendor Claim X-Ray v1data/build-021-engine-v1.json

Four disclosed verification paths and three non-binary verdicts over synthetic claims.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
02 / CREATED

What exists because we built it

021-A AI Vendor Claim / Procurement X-Ray

Breaks synthetic claims into evidence, scope, independent verification, and enforceable commitment.

Claim Verification Record v1

Reusable vendor-claim evidence and gap primitives for Build 025.

03 / ARCHITECTURE + DECISIONS

Why it works this way

Canonical versus derived copy is explicit

Title, job, B-web, and lineage are canonical; question, thesis, fixtures, thresholds, and interface language are derived.

Builds 011, 012, and 020 are concrete dependencies

The x-ray makes identity resolution, consequence controls, and reconstructable evidence visible.

Verification is scope-specific

A closed claim does not endorse the vendor, product, or use outside the stated context.

04 / AUDIT + RELEASE

How the work was checked

Machine-readable archivedata/build-021-archive-v1.json

Routes, lineage, retention, and deferred gates.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Privacy/supportdata/build-021-privacy-support-v1.json

Synthetic client-local fixture and procurement boundary.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Freshness/performancedata/build-021-freshness-performance-v1.json

Primary NIST sources and deterministic offline operation.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Browser fixturestests/build021.spec.ts

Verdicts, identity separation, export, 320px, and paired visual coverage.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
05 / PLANS + OPEN THREADS

What this build intentionally leaves forward

Release path

Complete static gates and Vercel deployment; keep authenticated browser, physical-device accessibility, GitHub-hosted CI, and media certification independent.

Future consumer

025 consumes cap:021.

06 / MEDIA

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.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.
07 / CANONICAL SOURCE INVENTORY

The repository files that preserve the implementation record

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.ts

These 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.