THE METHODOLOGY

Emergeneering™

A structured way to see unintended system behaviors the rules still permit, even after good controls are in place

In complex systems, the most important behaviors are often not explicitly designed.

They emerge through the interaction of parts: software, hardware, people, processes, decisions, and environments. Individually, each piece may make sense. Together, they can produce outcomes no one fully anticipated. That is where risks take shape.

What Is Emergeneering

Emergeneering is Firelight Logic’s structured methodology for understanding and shaping emergent behavior in complex systems. It brings together two realities:

  1. Emergence — the behaviors and outcomes that appear only when parts of a system interact

     

  2. Engineering rigor — the discipline of systematically analyzing, testing, and shaping those outcomes

Together they go beyond what is documented, tested, or assumed — so teams can see a full range of what a system may still permit.

Emergeneering builds on the Monterey Phoenix (MP) behavior modeling framework and applies it in real-world contexts through Firelight Logic’s process, analysis, and MP Ember™ platform.

Why the Emergeneering approach exists

Most systems are designed, tested, and documented with care. Those processes examine the system as specified. They are not designed to systematically surface what the specified rules still permit:

  • Testing focuses on expected scenarios
  • Documentation reflects what is already specified
  • Expertise is often distributed across roles, teams, and perspectives

What is harder to see is how those elements behave together when combinations no one intended come into view. Gaps form between intent and what the system still allows — because that class of behavior was never examined as a whole.

Emergeneering exists to make those gaps visible before they surface as failure, disruption, exposure, or costly rework.

How this methodology works

Emergeneering applies a deliberate, step-by-step process to:

  • Model how a system or process is expected to behave
  • Explore how that behavior changes when conditions shift
  • Surface unintended interactions and edge-case scenarios
  • Identify where outcomes satisfy the rules and still diverge from intent
  • Develop ways to control, adapt, or redesign those behaviors

This is not about testing expected behaviors or validating what is already known or suspected; it is about surfacing a full range of permitted behaviors in scope — including unexpected ones that had not yet been identified as risks to close.

What Emergeneering makes possible

When teams can see a full range of behaviors their systems may still permit, they can:

  • Identify risks that would not appear in standard analysis
  • Understand how far a known issue or vulnerability may extend
  • Strengthen a design or a deployed system against previously overlooked conditions
  • Make decisions with a clearer view of what the system still allows
  • Reduce the likelihood of costly surprises

Instead of only reacting to what happens, teams gain the ability to anticipate and shape it.

Where this methodology is used

Emergeneering is used wherever complexity creates risk and incomplete visibility affects decisions, including

  • Cybersecurity and cyber-physical systems
  • Operational and infrastructure reliability
  • Safety-critical environments
  • Emergency management and response
  • Supply chain and logistics
  • Mission-critical workflows across industries

Emergeneering can be used in any environment where multiple elements interact — and where the consequences of those interactions matter.

From methodology to application

Ember_who_it_is_for

Emergeneering is the methodology.

The methodology is how Firelight Logic thinks about systems, approaches analysis, and guides teams toward clearer understanding. This approach builds on the MP framework, a behavior modeling language and approach originating from the Naval Postgraduate School. Firelight Logic applies this work through MP Ember, its independently developed platform that makes behavior modeling more accessible through modern workflows, visualizations, and analysis tools. Together, the methodology, framework, and platform allow teams to move from unexamined assumptions to scenario-driven visibility.

→ Learn more about Monterey Phoenix

A different way of seeing

Emergeneering changes what is in view. Rather than analyzing only intended, well-constrained behaviors, it accounts for how the system can act with the people, processes, and conditions around it – and detects behaviors that emerge through that interaction. When that shift happens, teams move from

  • reacting to problems → anticipating them
  • operating on assumptions → working from visibility
  • managing isolated parts → seeing the system as a whole

That changes the basis for the decisions that follow.