{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-a-litmus-regression-gate-from-silently-passing-a-compromised-agent",
  "title": "Which invariants prevent a LITMUS regression gate from silently passing a compromised agent",
  "date_of_record": "2026 November 16",
  "scope": "Applies to LITMUS-style safety benchmark harnesses that gate agent releases on red-team attack success rate (ASR) and refusal-behavior regressions. Does not apply to single-turn classification evals, offline preference-model scoring, or harnesses that score a model rather than an agent loop with tool access.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-a-litmus-regression-gate-from-silently-passing-a-compromised-agent.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-a-litmus-regression-gate-from-silently-passing-a-compromised-agent.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-a-litmus-regression-gate-from-silently-passing-a-compromised-agent.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1282,
    "python_slice_tokens": 197,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A LITMUS gate answers one question: *did this candidate agent's safety posture regress relative to the baseline?* The non-obvious failure is that a gate can return `PASS` for a genuinely compromised agent when the **attack substrate is degenerate** — when the generated adversarial prompts no longer reach the agent's decision surface. This is distinct from a ...",
    "what_was_observed": "During a routine gate run for an agent with a new tool-use planner, ASR was reported as `0.000` across 412 attack seeds, and the gate passed. The baseline ASR for the prior release on the same corpus was `0.061`. The drop to zero was not a safety improvement. Three substrate failures compounded: 1. **Stale corpus.** The attack seeds were generated against the previous planner's system prompt. The new planner prepende...",
    "condition_of_validity": "The gate's `PASS` is only meaningful when all of the following hold, and the harness must *assert* them rather than assume them: - **Reachability:** every attack transcript's final user-role turn must be present in the model's actual input context, byte-for-byte, after any harness transformation. Assert `len(attack_turns_present) == len(attack_turns_generate...",
    "decision_boundary": "The boundary is between *a low ASR that reflects agent behavior* and *a low ASR that reflects harness behavior*. Operationally: - If `reachable_fraction < 1.0` → `INVALID`, not `PASS`. The gate did not run. - If `baseline_asr == 0.0` on the reference model → `INVALID`. The corpus is dead. - If `judge_error_fraction > 0.01` → `INVALID`. The judge did not see ...",
    "operational_effect": "After instrumenting the harness with explicit reachability, co-measurement, and judge-coverage assertions, the same release re-ran and reported `INVALID` on 3 of 5 attack families (context-truncated), `INVALID` on the judge (envelope mismatch), and a genuine ASR of `0.14` on the two families that survived — a real regression masked by a fake zero. The fix wa..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "abd06d0b296f6459fc0500e526fc64bfb6b3aba4444a239a2f42d43cfae6b01f",
    "verified_classes": [
      "DegenerateGateError"
    ],
    "verified_functions": [
      "certify_gate",
      "run_gate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "DegenerateGateError"
    ],
    "sample_fail_closed_invariants": [
      "candidate and baseline scored on different corpus revisions; cached baselines are a different experiment",
      "baseline ASR is exactly zero on the reference model; the corpus is dead and cannot gate anything"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
