Place-readiness engine + evidence boundary
data/build-009-engine-v1.jsonTen local dimensions, inherited decision-gap score, status logic, provenance, and non-claims.
BUILD 009
Place-Sensitive Technology Readiness
Transferability is not a property of technology alone. Requirements must be tested against evidenced local capacity, prevailing hazards, access needs, operating systems, and legitimate local authority before a bounded pilot.
QUESTIONCan this technology work in this place?
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
Complete Build 009 archive
docs/builds/009/ARCHIVE.mdCanon, evidence boundary, direct Build 003 inheritance, privacy, lineage, and release placeholders.
Build 009 specification
docs/builds/009/SPEC.mdPurpose, product contract, engine inheritance, evidence and non-claims.
NIST Community Resilience Planning Guide
Supports local goals, collaborative planning, dependencies, prevailing hazards, infrastructure, and social/economic context.
NTIA local coordination
Supports meaningful involvement of local, territorial, Tribal, and underrepresented communities.
What exists because we built it
009-A Place-Sensitive Technology Readiness
Compare requirements with local capacity, record evidence/owners/mitigations, bound a pilot, and export a local record.
009-B Transfer Is a Place Question
Interactive place scenarios reshape feasibility and local authority in real time.
Place Readiness Engine v1
Ten-dimension local fit heuristic with explicit blockers, unknowns, mitigations, and three named states.
Why it works this way
Build 003 is concretely inherited
The engine directly calls decisionGapScore and decisionGapTier before assessing place fit.
Community authority is a gate
Local and affected-community authority can condition, pause, or stop the pilot.
Fit is not certification
The rubric does not prove safety, legality, legitimacy, reliability, adoption, procurement, or successful transfer.
Status is not color-only
Every visual state is named, scored, structured, and described.
How the work was checked
Machine-readable archive
data/build-009-archive-v1.jsonStructured routes, lineage, privacy, evidence boundary, and release state.
009 browser fixtures
tests/build009.spec.tsConditional default, constraint change, empty state, export, lifecycle, 320px, scenario, and local-authority behavior.
What this build intentionally leaves forward
Release path
Complete static gates, Chromium/WebKit matrix, accessibility, archive, media, preview, and exact-head certification.
Future consumers
Canonical Builds 045, 046, and 047 explicitly consume cap:009.
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 · 357.9 KB
FINAL PROPOSITION / TRANSFERABILITY IS A PLACE QUESTION.
SHA-256 ef2a1701fe88a7976dddb6c81b1721d5a4a6cf9749d91d948bcdb206df93496dReproducible 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/009/a/PlaceReadinessLab.tsxapps/web/app/100-builds/009/b/FeasibilityField.tsxpackages/release/src/decision-engines.tsdata/build-009-engine-v1.jsondata/build-009-archive-v1.jsondocs/builds/009/SPEC.mddocs/builds/009/ARCHIVE.mdtests/build009.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.