Search cases, suites, agents…⌘K
DEMO · synthetic data
Adversarial

Red Team

Red teaming is not a separate world — it is the adversarial concern of the same portable-eval system, plus a campaign layer on top. A campaign targets an agent with versioned attack packs and a probe budget; everything downstream reuses settled machinery: cases, datasets, suites, gates, promote-with-sign-off.

pre-release· blocking
Blocking. A pre-release campaign IS the adversarial row in the suite's release-gate policy — a zero-tolerance breach stops the ship.
continuous· background
Background. Scheduled probing of the last shipped build inside a synthetic sandbox tenant (§45) — non-blocking, but every catch feeds the findings queue below.

Findings queue

open findings from continuous campaigns — triage → permanent regression
1 critical1 high1 medium0 low
Recently promoted: RTF-1024 people.nav_injection_regress_004 — an attack that worked once, now a permanent regression.
Continuousscheduled background probing · feeds the queue
Pre-releasethe adversarial row of a release gate · blocking
Every campaign draws on AAG-owned, versioned attack packs (exfil@v2, injection@v3, …) — teams inherit the taxonomy and add product-specific probes. DeepTeam expands seed cases into generated variants, so the fleet gets new attacks without every team writing them.