INSTITUTION ROUTE · CITIES AND CRITICAL INFRASTRUCTURE
Infrastructure risk becomes financial risk through dependencies.
City, utility and infrastructure teams do not need another dashboard. They need a route from physical stress to financial exposure, owner action and a boundary a committee can read.
Founder-direct intake · NDA before data · Review-grade evidence
The map matters because the cascade matters. A flood, heat event, cyber incident, port closure or grid interruption becomes a financial problem only after it moves through dependencies. SAA makes that path legible: trigger, exposed assets, owners, evidence status and what cannot be claimed yet.
Four places city risk usually breaks.
The institution owns the consequence even when the dependency sits outside the department, outside the operator or outside the city boundary.
The dependency is outside the department.
Pain. Transport, water, power, hospitals and vendors report their own lane. The failure moves across all of them.
SAA. Dependency paths with owner tables and explicit evidence status.
The city sees symptoms, not pathways.
Pain. A hazard map does not tell a finance team which service, asset or counterparty is exposed.
SAA. Physical-to-financial translation from trigger to exposed operation.
Funding needs evidence before the event.
Pain. Grant, resilience and bond conversations weaken when the evidence is narrative only.
SAA. Review-grade packet: source trail, scenario context, action boundary and cannot-claim line.
The board packet decays.
Pain. Three months later, the committee remembers the slide but cannot reopen the number.
SAA. Evidence object with owner, source set, replay path and publication boundary.
Proof wall, with boundaries visible.
The public page shows safe, demo-stamped surfaces only. Deeper product captures and row-level outputs move through the evidence pack after review.
Municipal hazard posture
Flood, heat, drought and wildfire lanes are shown as review-grade posture, not as official resilience certification.
DR.CAP.01 · DR.CAP.09 · DR.CAP.10
Hazard-to-exposure posture, dependency-path cascade and adaptation triage are the public excerpt of the runnable catalog.
Early warning · Cooling centers · Tree canopy
Measures are shown as catalog entries and committee prompts, not certified project economics.
Eligibility narrative with evidence status
Grant and board-language drafts keep source status and cannot-claim boundaries attached.
280 factors × 9 categories
The taxonomy shows coverage and routing; missing inputs are marked instead of fabricated into a cascade.
Evidence before assertion
Every output carries the same discipline: numbers, sources, owner, replay path and cannot-claim boundary.
Exhibit surface
From physical trigger to owner action.
The second surface is treated as an exhibit, not decoration: a static, demo-stamped view of how a trigger becomes a cascade map, owner table and boundary note.
Four workflows for city and infrastructure teams.
Each workflow returns the same disciplined packet: cascade map, owner table, evidence status and boundary note.
City posture
National-to-street-level context for hazards, infrastructure classes and exposed operations where inputs support the lane.
Dependency paths
Ports, grids, utilities, hospitals, suppliers and critical facilities mapped as dependency paths, not isolated dots.
Adaptation triage
Measures are ranked as committee options with evidence grades, noise fraction and cannot-claim boundaries.
Funding and board packet
Grant, bond or committee narrative built from the same evidence object instead of a detached executive summary.
Capability excerpt.
Only the public-safe capabilities are summarized here. Technical routing and row-level implementation details remain in the evidence pack.
Hazard-to-exposure posture
Dependency-path cascade
Adaptation ROI triage
One evidence object travels through the route.
The output is not a loose report. It is a structured object that carries the facts, the owner and the boundary together.
Founder-direct intake
Bring one hard infrastructure workflow.
We map the trigger, exposed operation, owner path, evidence status and action boundary before any production claim.
Founder-direct intake · NDA before data · Review-grade evidence