> For the complete documentation index, see [llms.txt](https://docs.naorisquantumprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.naorisquantumprotocol.com/use-cases/smart-infrastructure.md). # Smart Infrastructure **Resilience for cities, logistics and utilities.** Smart infrastructure is long-lived, physically distributed, and safety-critical — the combination that makes central trust models fragile. ## Why it fits * **Distributed by nature** — a trust mesh suits estates with no natural centre * **Resilience** — no single point of failure or compromise * **Long lifetimes** — post-quantum from day one, for assets measured in decades * **Operational continuity** — verification is added beneath systems that cannot stop ## Typical applications * Energy grid and substation integrity * Water and utility SCADA environments * Transport and logistics networks * Municipal sensor and control systems --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.naorisquantumprotocol.com/use-cases/smart-infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.