The Method
We didn't set out to build a unified methodology. We set out to solve two different problems — how leaders rehearse high-stakes decisions, and how energy systems cascade into crisis. The method emerged when we noticed we were writing the same equations twice.
Three components. Two projects. One running system. Here's how they fit together.
Cascade Modeling
Mapping how shocks propagate across interconnected systems. The core question is not “what happens when X fails?” but “what else becomes possible — or impossible — once X has failed?” Cascade thinking treats second- and third-order effects as the primary object of analysis, because that is where real risk lives.
In Resilience Intelligence, this is the entire analytical framework — mapping how a disruption at the Strait of Hormuz propagates through fuel prices into food systems, or how interconnected vulnerabilities across UK infrastructure amplify rather than simply add.
In the decision engine: The LastPrompt engine applies cascade logic through interdependency multipliers — when cohesion is low, diplomacy outcomes are dampened; when infrastructure is weak, sustenance shocks amplify. Risk in the simulation is compound, not additive. The same structure that maps energy chokepoints models organisational fragility.
Chronosymbiosis
A framework for weaving temporal dynamics into decision models so that time becomes a design variable, not just a constraint. Where conventional analysis asks “what is true now?”, chronosymbiosis asks “what becomes true over time, and how does present action shape that trajectory?” The relationship between present and future is reciprocal: decisions made now alter the conditions under which future decisions will be made.
In Resilience Intelligence, this is visible in the live dashboards — not a snapshot of today's supply, but an ongoing map of how exposure accumulates and compounds over time.
In the decision engine: Chronosymbiosis is operationalised as temporal_symbiosis — the sixth and final rubric criterion by which every decision is evaluated. It is not a bonus category. It is the measure of whether the decision-maker understood that their choices were reshaping the future conditions they would have to navigate.
Observer Patch Holography (OPH)
Bernhard Mueller's framework, drawn from holographic principles, in which each observer holds a partial ‘patch’ of a complex system — a bounded, coherent slice of a reality too large to see whole. Rather than pretending to a god's-eye view, OPH works with the patch: making its boundaries explicit, navigating from within them, and understanding how patches from different observers combine to form a fuller picture without ever resolving into a complete one.
In Resilience Intelligence, OPH structures how regional analysis on each OilWatch platform is framed — each site holds a patch; none claims to hold the whole.
OPH explained at last-prompt.com →In the decision engine: Each AI advisor in LastPrompt carries a distinct decisionBias weight object — a formalised observer patch. No single advisor has the full picture. The quality of a decision emerges from navigating between patches, not from finding the one advisor who is right. OPH is the mechanism through which structured navigation of uncertainty becomes possible.
One System, Not Three Components
The three components are not a theoretical framework waiting to be applied. They are already running. The LastPrompt engine applies cascade multipliers, evaluates temporal symbiosis, and routes decisions through OPH-structured advisor patches — in every session, across every scenario skin.
The synthesis paper — currently in preparation — establishes the formal correspondence: that institutional silo structure maps directly to professional horizon (OPH); that the methodology gap between disciplines is a translation gap between patches; that the interaction matrix in cascade modeling is the externalised form of the cognitive feedback loops chronosymbiosis describes. Same problem. Two scales. One method.