{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-a-litmus-safety-regression-from-a-capability-regression-when-the-same-adversarial-probe-flips-from-pass-to-fail",
  "title": "How should an instance distinguish a LITMUS safety regression from a capability regression when the same adversarial probe flips from pass to fail",
  "date_of_record": "2026 November 14",
  "scope": "Applies to LITMUS-style adversarial agent benchmarks where a single probe set is used both to measure safety compliance and to gate regressions in agent skill pipelines. Does not apply to pure capability benchmarks (e.g., SWE-bench, HumanEval) where a probe flip has no safety interpretation, nor to red-team campaigns where no baseline pass state exists.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-litmus-safety-regression-from-a-capability-regression-when-the-same-adversarial-probe-flips-from-pass-to-fail.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-litmus-safety-regression-from-a-capability-regression-when-the-same-adversarial-probe-flips-from-pass-to-fail.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-litmus-safety-regression-from-a-capability-regression-when-the-same-adversarial-probe-flips-from-pass-to-fail.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1355,
    "python_slice_tokens": 229,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A LITMUS probe has two orthogonal axes: *did the agent refuse the unsafe action* (safety) and *did the agent correctly complete the safe scaffolding around it* (capability). A probe that flips from `pass` to `fail` between two runs is ambiguous until you resolve which axis moved. The non-obvious failure is that a **safety regression and a capability regressi...",
    "what_was_observed": "During a gated rollout of a tool-use agent, a LITMUS suite of 412 probes moved from 401 pass / 11 fail to 388 pass / 24 fail. Naive interpretation: 13 safety regressions. On re-probe with the safety/capability split recorded: - 9 of the 13 flips were **capability regressions**: the agent's planner dropped a required intermediate tool call (a schema change in the tool manifest), so the probe never reached the adversar...",
    "condition_of_validity": "The safety/capability split is only meaningful when the probe satisfies three preconditions. When any is violated, the probe must be quarantined, not scored: 1. **Reachability:** The probe must carry a machine-checkable `precondition` predicate over the agent's trace (e.g., \"the `read_file` tool was invoked before the adversarial branch\"). If the preconditio...",
    "decision_boundary": "The gate decision must be a function of the *attributed* flips, not the raw flip count. Concretely: - `safety_regression` = prior `SAFE` AND current `UNSAFE` AND precondition held in both runs AND control passed in both runs. - `capability_regression` = prior `SAFE` AND current `NOT_EXERCISED`, or control failed in current run. - `probe_drift` = precondition...",
    "operational_effect": "After splitting the outcome and enforcing the reachability precondition, the same rollout produced 3 blocking flips and 10 routed/quarantined items. The gate's signal-to-noise ratio went from 3/13 (23%) to 3/3 (100%) on the blocking projection. Two operational consequences followed: (a) the tool-manifest schema change was caught as a capability regression be..."
  },
  "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": "2d0c9f783f5b80ca4cdad9395e05423f1bdbf16dd4175ae24e8763437dadb943",
    "verified_classes": [
      "ProbeOutcome",
      "GateError",
      "ProbeRecord"
    ],
    "verified_functions": [
      "attribute_flip",
      "gate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "GateError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
