AI workflow consequences do not stop at a model output or institutional boundary. Direct subjects, households, workers, and communities need separate visibility, representation, notice, correction, and recourse.
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-022-engine-v1.jsonAffected-person nodes, protection gaps, inherited workflow and handoff states, and a disclosed prioritization heuristic.
Grounds context-sensitive mapping of expected impacts.
Maps distinct affected groups, notice, representation, recourse, inherited control states, and local export.
Changing a workflow assumption lights up additional human-impact nodes.
Reusable primitives for Builds 048 and 077.
Title, job, B-Web, and lineage are canonical; all other public copy and heuristics are derived.
The engine executes the workflow scan and regulated-handoff assessment.
Direct subjects, households, workforce, and communities are not collapsed.
The signal prioritizes investigation and does not establish probability, causation, law, or lived experience.
data/build-022-archive-v1.jsonRoutes, lineage, privacy, deferred gates, and lifecycle.
data/build-022-privacy-support-v1.jsonSynthetic client-local state and real-deployment boundary.
data/build-022-freshness-performance-v1.jsonPrimary NIST sources and deterministic offline operation.
tests/build022.spec.tsDistinct records, protection changes, export, 320px, and paired visual coverage.
Complete static gates and exact-head Vercel deployment; keep authenticated browser, physical-device accessibility, GitHub-hosted CI, and media certification independent.
048 and 077 consume cap:022.
CURRENT VERIFIED MEDIA / 30-second film · 352.0 KB
FINAL PROPOSITION / SHOW WHO CAN BE AFFECTED BY AN AI WORKFLOW AND HOW CONSEQUENCES TRAVEL TO THEM.
SHA-256 709eb4b5b46bf87f855a9b18d47df8838358c4b0f57eb531dac8c4ed6704c2f9Reproducible 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/022/a/HumanConsequenceLab.tsxapps/web/app/100-builds/022/b/ImpactField.tsxpackages/release/src/human-consequence-engine.tsdata/build-022-engine-v1.jsondata/build-022-archive-v1.jsondocs/builds/022/SPEC.mddocs/builds/022/ARCHIVE.mdtests/build022.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.