Data is portable only when a complete, readable, versioned export can map into another system without silently losing required fields, provenance, or semantic structure.
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-035-engine-v1.jsonVersioned required-field, machine-readability, provenance, and target-mapping rules over a synthetic fixture.
Tests a synthetic export package, exposes data loss, repairs the target mapping, and exports an exact record locally.
Makes a record attempt to leave a source system and survive a target import.
Reusable data-exit infrastructure for resilience, care, personal context, collaboration, and commons builds.
Title, job, B-Web, and lineage are frozen canon; schema, mappings, fixture values, scores, statuses, and copy are derived.
Portability inherits explicit schema, reversible provenance, and version/change trace.
A file must preserve required structure, readability, provenance, and a usable target mapping.
PORTABLE FIXTURE does not establish legal compliance, vendor compatibility, semantic equivalence, or migration success.
data/build-035-archive-v1.jsonRoutes, exact lineage, privacy boundary, and deferred gates.
data/build-035-privacy-support-v1.jsonSynthetic browser-local transfer with no real account data.
data/build-035-freshness-performance-v1.jsonVersioned deterministic offline-after-load operation.
tests/build035.spec.tsData loss, repaired package, local export, 320px, and accessible B transfer.
Authenticated live browser, physical-device/manual accessibility, GitHub-hosted CI, real-system interoperability review, and LinkedIn media certification remain separate.
036, 045, 065, 067, 071, and 099 consume cap:035.
CURRENT VERIFIED MEDIA / 30-second film · 113.9 KB
FINAL PROPOSITION / Portability means usable independence.
SHA-256 a43cee2efc68e4069625c2f229d6d3a448142da4010ef6e32a3a41e7dea20f7fReproducible 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/035/a/PortabilityLab.tsxapps/web/app/100-builds/035/b/DataJourney.tsxpackages/release/src/data-portability-engine.tsdata/build-035-engine-v1.jsondata/build-035-archive-v1.jsondocs/builds/035/SPEC.mddocs/builds/035/ARCHIVE.mdtests/build035.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.