THE FRAMEWORK
Monterey Phoenix
The behavior modeling framework this work is built on
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—examining how interactions between components, people, processes, and environments produce different outcomes.
At its core, Monterey Phoenix enables the generation and exploration of behavior paths, making it possible to examine not just what a system is intended to do—but what it may actually permit.
In fact, unlike traditional approaches that only sample expected or intended behaviors, MP systematically generates all possible behavior paths within a defined scope— revealing outcomes that would otherwise stay hidden.
What MP makes possible
Most systems are understood in terms of how they are designed to behave.
What’s harder to see is everything the system may actually allow when conditions shift, interactions compound, or assumptions don’t hold.
Monterey Phoenix enables that deeper level of visibility.
With it, teams can:
- Map how a system or process actually works using their own knowledge and language
- Explore how that system behaves across a range of conditions
- Examine every possible behavior path in scope—not just the intended or expected paths
- Identify risks, gaps, and unintended interactions
- Surface assumptions that influence decisions without being clearly articulated
This creates a clearer, more complete view of how a system behaves within its real boundaries.
How MP fits into the work
Monterey Phoenix is the foundational framework behind this work.
At Firelight Logic, it is applied through the Emergeneering™ methodology—a structured approach to examining real-world systems—and through MP Ember™, our platform that makes this capability accessible through modern workflows, visualization, and analysis tools.
Together, these elements allow teams to move beyond assumptions and documentation into scenario-driven visibility.
How it works
Monterey Phoenix provides the underlying modeling capability that allows system behavior to be explored and analyzed exhaustively.
Within the Emergeneering process, this typically involves:
Build the Model
Describe how a system is expected to work using plain language—defining events, decisions, and interactions.
Generate and explore behavior paths
Run the model to generate possible behavior paths (traces) within a defined scope, allowing different conditions and inputs to be examined.
Surface interactions and outcomes
Refine and iterate
Update the model and repeat the process to better understand, control, or reshape system behavior.
THE RESULT IS NOT A SINGLE ANSWER.
It is a structured view of the behaviors the system permits—giving teams a way to discover, evaluate, and work through outcomes that would otherwise remain unseen.
Where this is used
Monterey Phoenix 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
It has supported work with:
- Naval commands
- Defense agencies
- National laboratories
- And other organizations responsible for complex, high-stakes systems
How organizations and teams engage with this work
Organizations engage this work in different ways.
Some bring specific systems, questions, or concerns into structured environments where they are explored through modeling and scenario analysis.
Others engage in focused, private work—where a specific system, process, or concern is examined directly within a controlled and confidential setting.
Others develop internal capability—learning how to apply this approach directly within their own teams.
In all cases, the goal is the same:
To create visibility into how systems behave, so decisions can be made with a more complete understanding of what is actually possible.
From visibility to better decisions
Monterey Phoenix does not replace expertise, testing, or documentation.
It extends them.
By making system behavior visible, it gives teams 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 the full range of behavior is visible, decisions are no longer based on partial understanding.