Scenario Authoring

Define behavior, not infrastructure. NetMetria executes intent and derives all realizations deterministically.

Intent Over Infrastructure

Scenarios describe what happens, not how it is physically implemented.

You do not define networks, devices, or packet structures. You define behaviors and relationships.

What You Define

Entities

Logical actors and systems involved in the scenario.

Behaviors

Actions performed by entities over time.

Relationships

How entities interact and influence each other.

Timing

When behaviors occur within the deterministic timeline.

Conditions

Constraints that govern when behaviors execute.

Intent

The purpose of the scenario, independent of realization.

What You Do Not Define

No Networks

No topology, routing, or infrastructure configuration.

No Packet Crafting

No manual protocol construction or traffic replay.

No System Emulation

No operating systems, services, or virtual machines.

Separation of Intent and Realization

Scenario definitions are independent of how outputs are produced.

Intent
Execution
Telemetry
Outputs

Addressing, protocols, sessions, and artifacts are resolved during realization. They are not part of scenario semantics.

Deterministic Scenario Execution

The same scenario produces identical telemetry and outputs every time.

Reusable and Extensible

Scenarios are portable and independent of environment.

From Definition to Execution

Once defined, scenarios are executed deterministically, observed into telemetry, and realized into output families without requiring additional configuration.