Workflow scanner engine
data/build-013-engine-v1.jsonDirected stage traversal, inherited Build 012 assessment, control coverage, propagation exposure, gaps and non-claims.
BUILD 013
AI Workflow Consequence Scanner
AI consequence is produced by an end-to-end workflow. A risk entering one stage can survive every downstream handoff when ownership, control, stop authority, or monitoring is missing.
QUESTIONWhere does consequence enter and travel?
STRUCTURED PUBLIC BUILD ARCHIVE
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.
5 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.
What informed the build
NIST AI RMF Core
Grounds lifecycle interdependence, distributed visibility, mapped context, measurement and ongoing management.
NIST SP 800-218A
Grounds AI-specific secure practices across the software development lifecycle.
What exists because we built it
013-A AI Workflow Consequence Scanner
Trace risks through six stages, remove controls, expose gaps and export locally.
013-B Follow the Consequence
An interactive risk circuit illuminates downstream propagation.
AI Workflow Scanner Engine v1
Reusable directed propagation and stage-control assessment.
Why it works this way
Build 012 is concretely inherited
The scanner directly calls assessAIUseControls and exposes its status.
Workflow stages—not model boundaries—define scope
Intake, data, model, decision, action and monitoring remain visible.
Every stage needs four control properties
Owner, control, stop authority and monitoring are independently inspectable.
Exposure is not probability
The score prioritizes gaps; it does not predict harm or approve deployment.
How the work was checked
Machine-readable archive
data/build-013-archive-v1.jsonRoutes, lineage, privacy and consumers.
Privacy/support
data/build-013-privacy-support-v1.jsonClient-local state and competent-review boundary.
Freshness/performance
data/build-013-freshness-performance-v1.jsonCurrent primary sources and offline graph traversal.
Browser fixtures
tests/build013.spec.tsContained, propagation, reset, export, lifecycle, 320px and B-state coverage.
What this build intentionally leaves forward
Release path
Complete static gates, Chromium/WebKit matrix, media, preview and exact-head certification.
Future consumers
022, 025, 032 and 041 consume cap:013.
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 · 330.5 KB
FINAL PROPOSITION / FOLLOW THE CONSEQUENCE THROUGH THE WORK.
SHA-256 380335870b65f9a6047866d8b2be39bece7463cb585e433127ff333cb80a3ebfReproducible 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/013/a/WorkflowScanner.tsxapps/web/app/100-builds/013/b/RiskCircuit.tsxpackages/release/src/decision-engines.tsdata/build-013-engine-v1.jsondata/build-013-archive-v1.jsondocs/builds/013/SPEC.mddocs/builds/013/ARCHIVE.mdtests/build013.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.