SPEC.md

# Build 009 — Place-Sensitive Technology Readiness

## Frozen canon

- **Job:** Test whether a technology can work in a particular place before assuming transferability.
- **A:** A local readiness lab that compares technology requirements with evidenced local capacity.
- **B:** Place constraints reshape a feasibility map in real time.
- **Uses:** Build 003.
- **Creates:** `cap:009`.
- **Explicit consumers:** 045, 046, 047.

## Product contract

The user names the technology, place, and unresolved decision; scores the decision gap inherited from Build 003; compares requirements with local capacity across ten dimensions; records evidence, owners, and mitigations; and defines a pilot, fallback, stop condition, and community authority. The result is **PLACE READY**, **CONDITIONAL**, or **NOT READY**.

## Concrete inheritance

Build 009 calls Build 003's `decisionGapScore` and `decisionGapTier` directly. Place fit does not erase the upstream question of whether a recurring, consequential, ambiguous, fragmented decision gap exists.

## Evidence boundary

The NIST Community Resilience Planning Guide supports local goals, stakeholder collaboration, dependencies, prevailing hazards, and social/economic context. NTIA local-coordination guidance supports meaningful involvement of state, local, territorial, Tribal, and underrepresented communities. W3C accessibility guidance supports evaluating diverse access needs rather than assuming a single user context.

These sources inform the dimensions. The weights, thresholds, fit score, and three statuses are product heuristics.

## Non-claims

The lab does not prove legal compliance, safety, cultural legitimacy, infrastructure reliability, adoption, procurement approval, or successful technology transfer. Local experts and affected communities retain authority. A high score authorizes only a bounded pilot under the stated controls.

## Privacy

All interaction is client-local. Export is user-initiated. No form state is sent to a server by this artifact.