Resilience becomes inspectable when every capability declares dependencies, local data, fallback behavior, queued recovery, degradation state, and a portable exit path before failure occurs.
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-036-engine-v1.jsonVersioned dependency, capability, local-fallback, queued-recovery, and survival-state rules over a synthetic fixture.
Cuts synthetic dependencies, marks capability survival, enables queued fallbacks, and exports locally.
Severs a dependency field and moves the product through connected, degraded, and recovery-queued states.
Reusable offline/resilience infrastructure for personal context, smart environments, care continuity, collaboration, and commons builds.
Title, job, B-Web, and lineage are frozen canon; dependencies, capabilities, fallbacks, states, and copy are derived.
Offline state inherits consent, minimization, change trace, and portable exit boundaries.
A local fallback may preserve partial work without claiming full online equivalence.
SURVIVES does not establish uptime, disaster recovery, load tolerance, security, or real offline behavior.
data/build-036-archive-v1.jsonRoutes, exact lineage, privacy boundary, and deferred gates.
data/build-036-privacy-support-v1.jsonSynthetic browser-local state with no installed persistent offline store.
data/build-036-freshness-performance-v1.jsonVersioned deterministic offline-after-load operation.
tests/build036.spec.tsDependency cuts, fallback hardening, local export, 320px, and accessible B network state.
Authenticated live browser, physical-device/manual accessibility, GitHub-hosted CI, real outage/service-worker review, and LinkedIn media certification remain separate.
049, 055, 065, 067, 071, and 099 consume cap:036.
CURRENT VERIFIED MEDIA / 30-second film · 108.7 KB
FINAL PROPOSITION / Design disconnection before it happens.
SHA-256 6a4fa604b59227f7f5a6ba0063b7b065c60bd2beb78ccc79cff8993cd401b6fbReproducible 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/036/a/SurvivalLab.tsxapps/web/app/100-builds/036/b/DependencyCut.tsxpackages/release/src/resilience-survival-engine.tsdata/build-036-engine-v1.jsondata/build-036-archive-v1.jsondocs/builds/036/SPEC.mddocs/builds/036/ARCHIVE.mdtests/build036.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.