Governed engine record
data/build-002-engine-v1.jsonThe preservation/anchor contract and its limits are recorded as product/engineering heuristics.
BUILD 002
Multi-Audience Meaning Architecture
Audience adaptation should transform register and explanation while preserving a separate source-of-truth object, explicit anchors, and an independent drift check.
QUESTIONCan the language change without the truth moving?
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.
4 of 4 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
Public record source
docs/builds/002-public-record.mdThe original visitor-facing method/evidence/limits record created during the 002 build.
Browser-AI capability investigation
Local generation/translation was treated as optional progressive enhancement; an opaque CDN NLI evaluator was rejected until it could be pinned/versioned and governed.
What exists because we built it
002-A working tool
Adapt one source claim for a selected audience while preserving locked facts, numbers, uncertainty, names, and negation.
002-B interactive visual
Audience doors alter expression while truth anchors stay visibly fixed.
Public build record
Making, method, evidence, and limitations.
Why it works this way
Generation and verification stay separate
A fluent rewrite is never treated as its own proof of preservation.
Browser AI is not first-value dependency
Core value remains available without a model/network call.
Anchor checks are alarms, not equivalence proof
Passing the preservation contract does not establish semantic/cultural equivalence.
How the work was checked
002 release record
docs/builds/002-release-record.mdDetailed certification-era release record and unresolved-manual distinctions.
Shared first-tranche certification
docs/builds/001-003-certification-ledger.md001–003 release matrix, security review, artifact ledger, privacy/support and freshness/performance records.
What this build intentionally leaves forward
Future governed evaluator path
A stronger semantic evaluator remains possible only when versioning, provenance, fallback, and domain validation can be made inspectable.
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 · 374.4 KB
FINAL PROPOSITION / CHANGE THE LANGUAGE. KEEP THE TRUTH ANCHORED.
SHA-256 9ee5da5c6711577d749f205d21b3818df6544b91f78057406a5700926b7951e6Reproducible 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/002/a/MeaningArchitecture.tsxapps/web/app/100-builds/002/b/MeaningDoors.tsxdata/build-002-engine-v1.jsondocs/builds/002-public-record.mddocs/builds/002-release-record.mddocs/builds/001-003-certification-ledger.mddocs/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.