The doctrine behind the framework, in print.
Two books by ASR founder Syed Abid Shah on keeping critical infrastructure — and the authority that runs it — operating under permanent instability.
Decision Sovereignty
A Governance Architecture for the Authority Layer of Critical Infrastructure Resilience
A system can remain technically intact and still fail — if the authority to direct it collapses.
Resilience engineering focuses almost entirely on physical and technical survival: uptime, redundancy, recovery times. But when a crisis hits critical infrastructure, a deeper failure mode emerges — the collapse of legitimate authority to make and execute decisions.
Decision Sovereignty tackles that overlooked layer, providing a rigorous operational doctrine for decision-making under severe systemic disruption. It moves from foundational theory to practical application: dismantling governance bottlenecks, clarifying the mechanics of command when automated systems trigger, and keeping legitimate authority alive alongside the infrastructure it governs.
- The authority layer of resilience
- Command continuity when central control goes dark
- Governance bottlenecks under disruption
- Human authority alongside automated systems
Boards, crisis leadership, and operators responsible for critical infrastructure governance.
Syed Abid Shah
as
ArchitectureDesigning Critical Systems for Continuity Under Permanent InstabilitySyed Abid Shah
Resilience as Architecture
Designing Critical Systems for Continuity Under Permanent Instability
Instability is not an event to recover from. It is the operating condition to design for.
Most resilience programs treat disruption as an exception — something to absorb, recover from, and return to normal after. Resilience as Architecture starts from the opposite premise: in interconnected critical systems, instability is permanent, and continuity has to be designed in from the start.
The book sets out the doctrine behind the ASR framework — mapping dependencies across physical, digital, and institutional layers, locating the pivot nodes whose failure cascades across them, and structuring systems so each site can keep operating when the centre cannot.
- Resilience as a design discipline, not a recovery plan
- Cross-domain dependencies and pivot nodes
- Continuity under permanent instability
- Distributed operation when central control fails
Engineers, architects, and executives designing or governing energy, port, grid, and operations infrastructure.
Syed Abid Shah
Bring the doctrine to your leadership team.
Ask about team copies, author briefings, and working sessions built around either book.