PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

RANGE-02

Evaluation-to-Regression Lifecycle

An observed failure becomes durable security capability when it is converted into a replayable regression fixture.

governed lifecycle

Evaluation lifecycle
  1. 1
    Define the scenario
    Record target assumptions, preconditions, allowed actions, and expected evidence.
  2. 2
    Execute under control
    Run within explicit authorization, data, rate, and environment limits.
  3. 3
    Observe the result
    Capture model, retrieval, tool, agent, and external behavior.
  4. 4
    Reproduce and challenge
    Repeat the behavior and test alternative explanations.
  5. 5
    Create the regression fixture
    Preserve the minimum replayable inputs, assertions, and evidence hooks.
  6. 6
    Rerun after change
    Determine whether the failure is closed, residual, rejected, or still reproducible.
Retest loop returns to Execute under control
What did the rerun prove?
  • Closed
  • Residual
  • Still reproducible
  • Inconclusive

About this figure

Evaluation-to-Regression Lifecycle describes a governed security workflow in which an observed failure is not treated as a one-off anomaly but as durable evidence. A scenario is defined, executed under controlled conditions, and its result is observed and challenged through reproduction. Once the failure is confirmed, it is converted into a replayable regression fixture that captures the behavior precisely enough to be rerun after subsequent changes. The lifecycle closes the loop between evaluation and enforcement, turning adversarial findings into lasting checks that preserve the capability to detect the same failure class in future revisions.

Embed in a route

<FigureFromSource sourcePath="content/publications/figures/products/adversarial-range.dsl.md" figureId="RANGE-02" />

Citation

Evaluation-to-Regression Lifecycle (RANGE-02). AI Security LLC Figure Library. https://aisecurity.llc/publication-dsl/figures/RANGE-02