# Adversarial Range Figures
Scenario Pack Architecture
Reusable scenario packs organize prompt, retrieval, tool, authority, multimodal, and workflow abuse into repeatable tests.
Ecosystem map with scenario packs surrounding a controlled execution and evidence core.
- Scenario execution
- Evidence capture
- Replay and regression
Evaluation-to-Regression Lifecycle
An observed failure becomes durable security capability when it is converted into a replayable regression fixture.
Lifecycle from scenario design and execution through failure reproduction, evidence review, fixture creation, rerun, and regression state.
- 1Define the scenarioRecord target assumptions, preconditions, allowed actions, and expected evidence.
- 2Execute under controlRun within explicit authorization, data, rate, and environment limits.
- 3Observe the resultCapture model, retrieval, tool, agent, and external behavior.
- 4Reproduce and challengeRepeat the behavior and test alternative explanations.
- 5Create the regression fixturePreserve the minimum replayable inputs, assertions, and evidence hooks.
- 6Rerun after changeDetermine whether the failure is closed, residual, rejected, or still reproducible.
- Closed
- Residual
- Still reproducible
- Inconclusive
Human-Guided and Autonomous Modes
Analyst-guided, model-guided, and replay-driven testing serve different purposes and require different controls.
Comparison of analyst-guided exploration, model-guided scenario execution, and deterministic replay.