THE FRAMEWORK
Monterey Phoenix
Monterey Phoenix (MP) is a behavior modeling framework originating from the Naval Postgraduate School. It provides a structured way to model and explore how systems behave across conditions by examining how interactions among components, people, processes, and environments produce different outcomes. At its core, MP enables the generation and exploration of behavior paths, making it possible for teams to examine not only what a system is intended to do but also what it may still permit. Unlike approaches built to sample expected or intended behaviors, MP systematically generates all possible behavior paths within a defined scope — revealing outcomes that would otherwise stay out of view.
What Monterey Phoenix Makes Possible
Most systems are understood in terms of how they are designed to behave. What is harder to see is everything the system may still allow when conditions shift, interactions compound, or assumptions do not hold. MP is built for that visibility.
With MP, teams can
- Map out the rules for how a system or process is intended to work, using their own knowledge and language
- Examine the behavior paths in scope — not only those that are expected, but all paths the rules still permit
- Explore how that system might behave when the rules change
- Identify risks, gaps, and unintended behaviors and interactions
- Surface assumptions that are shaping decisions without being clearly captured
MP provides a clearer view of how a system could still behave within the rules as specified. It reveals “extra” behaviors along with intended behaviors.
How Monterey Phoenix fits into our work
MP is the computational framework behind our work. Firelight Logic applies it through Emergeneering™ — our structured approach for examining and shaping emergent behavior in complex systems — and through MP Ember™, the platform that makes this framework and approach useable in modern workflows, visualization, and analysis. Together they move teams from unexamined assumptions to scenario-driven visibility.
How Monterey Phoenix fits into the Emergeneering process
MP provides the underlying modeling capability that lets system behavior be explored within a defined scope. In the Emergeneering process, that typically means:
Build the Model
Describe how a system is expected to work in plain language, defining rules for events, decisions, and interactions.
Generate and explore behavior paths
Run the model to generate possible behavior paths (traces) in scope, so different combinations and conditions can be examined together.
Surface interactions and outcomes
Inspect those paths for interactions, edge cases, and behaviors that satisfy the rules but diverge from intent.
Refine and iterate
Update the model and repeat the process to better understand, control, or reshape system behavior.
The result is a structured view of behavior that the rules — as currently understood and captured — permit, giving teams a way to discover, evaluate, and work through outcomes that would otherwise remain unseen.
Where Monterey Phoenix is used
MP has been applied across environments where complexity shapes outcomes and visibility is critical, including
- Cybersecurity and cyber-physical systems
- Operational and infrastructure environments
- Safety-critical systems
- Emergency response and coordination
- Supply chain and logistics
MP has supported
- Naval commands
- Defense agencies
- National laboratories
- And other organizations responsible for complex, high-stakes systems
How organizations and teams engage with Monterey Phoenix
We offer three primary ways to engage with MP:
- Bring a system, question, or concern to one of our experiential programs for modeling and scenario analysis by students under the guidance of mentors and coaches.
- Engage in a focused analysis on a specific system, process, or concern in a controlled, confidential setting.
- Build internal capability and apply this approach directly within their own teams.
In each case the goal is the same: to create visibility into how the system behaves, so decisions rest on a more complete view of what it still permits.
From visibility to better decisions
MP does not replace expertise, testing, or documentation. It extends them. By making latent, permitted system behaviors visible, teams have a stronger basis for
- Identifying what needs attention
- Understanding how far a risk may extend
- Evaluating scenarios before they occur
- Making decisions with a more complete view of the system
When a full range of behavior is visible, decisions no longer have to rest on the expected paths alone.