Use cases — evidence before deployment claims

Use cases describe intended workflows and historical demonstrations. They do not establish a current deployment, customer use, signed runtime receipt, or formal guarantee. Verify source, runtime, proof, and artifact evidence independently.

Use case	Evidence posture
Investor and developer evaluation	Current documentation journey; deployed source identity comes from /deployment.json
Greene counter-UAS demonstration	Source/historical flow; recheck killinchu route readiness beyond health
Sovereign-government deployment	Design and admission checklist; UDS artifact/deployment UNAVAILABLE
Warhacker / UDS briefing	Historical briefing plan; no current cluster or attestation witness
Iron Dome Brain	Conceptual decision-support architecture; no autonomous lethal authority

Promotion rule

A use case becomes operational only when it binds immutable source/image revisions, current route and auth results, raw outputs, artifact-specific verification, failure/rollback tests, protected deployment evidence, and independent live readback. Until then use MODELED, HISTORICAL, ROADMAP, or UNAVAILABLE.

See /status, /compliance, and /evidence/.