Regulated work does not become safe because every organization has its own box. Responsibility, evidence, permission, acceptance, incident duties, records, and recourse must survive every transfer.
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-017-engine-v1.jsonCross-organization responsibility-gap detection that concretely inherits Build 016’s workflow and handoff assessment.
Grounds explicit allocation and documentation of manufacturing activities while preserving each party’s applicable CGMP responsibilities.
Grounds bounded uses, safeguards, reporting, downstream restrictions, records, return or destruction, cure, termination, and organizational responsibility in the HIPAA business-associate context.
Maps organizations and cross-institution controls, exposes a broken data transfer, and exports locally.
An interactive institutional diagram reveals five hidden transfer questions.
Reusable primitives for later state, escalation, implementation, consent, and regulated-system builds.
The engine converts organizations and transfers into the legal workflow nodes and nine-field handoffs consumed by assessLegalWorkflow.
The mapper allocates work and controls without implying that a contract transfers or eliminates obligations imposed by governing law.
A technically successful transfer can still fail because its purpose, authority, incident response, or affected-person remedy is missing.
Every real use requires the correct jurisdiction, market, product, activity, agreement, facts, and competent reviewers.
data/build-017-archive-v1.jsonRoutes, lineage, privacy, deferred gates, and lifecycle.
data/build-017-privacy-support-v1.jsonClient-local operation and legal/compliance boundary.
data/build-017-freshness-performance-v1.jsonCurrent primary sources and offline deterministic operation.
tests/build017.spec.tsIntact, broken controls, reset, export, lifecycle, 320px, and paired-visual coverage.
Complete local gates, Vercel deployment, and live browser verification; keep GitHub-hosted CI and media certification pending until Actions capacity returns.
018, 019, 022, 043, 044, 048, 065, 069, 077 and 093 consume cap:017.
CURRENT VERIFIED MEDIA / 30-second film · 362.9 KB
FINAL PROPOSITION / FIND WHERE RESPONSIBILITY, EVIDENCE, CONSENT AND ACCOUNTABILITY DISAPPEAR BETWEEN ORGANIZATIONS.
SHA-256 21bdce0ff8c819e202a4c2d7b32ef5a28e7bc3d088e4329ecb7317fc8fb54bbfReproducible 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/017/a/RegulatedHandoffLab.tsxapps/web/app/100-builds/017/b/BetweenTheBoxes.tsxpackages/release/src/decision-engines.tsdata/build-017-engine-v1.jsondata/build-017-archive-v1.jsondocs/builds/017/SPEC.mddocs/builds/017/ARCHIVE.mdtests/build017.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.