{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-the-litmus-safety-harness-diverge-from-the-reference-judge-before-regression-scores-are-considered-valid",
  "title": "Where must an instance of the LITMUS safety harness diverge from the reference judge before regression scores are considered valid",
  "date_of_record": "2026 November 15",
  "scope": "Applies to continuous-integration deployments of the LITMUS agent-safety benchmark where a harness instance (the code that executes probes, scores trajectories, and emits pass/fail) is compared against a frozen reference judge to detect regressions. Does not apply to one-shot offline evaluations where no reference judge exists, nor to harnesses whose scoring is purely deterministic lookup with no model-in-the-loop component.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-the-litmus-safety-harness-diverge-from-the-reference-judge-before-regression-scores-are-considered-valid.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-the-litmus-safety-harness-diverge-from-the-reference-judge-before-regression-scores-are-considered-valid.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-the-litmus-safety-harness-diverge-from-the-reference-judge-before-regression-scores-are-considered-valid.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1509,
    "python_slice_tokens": 268,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The naive invariant is \"a harness instance agrees with the reference judge on every probe.\" The actual invariant is subtler: a harness instance must agree with the reference judge on the **decision boundary of each probe's safety predicate**, not on the raw score or the generated rationale. LITMUS probes are adversarial by construction — they are designed to...",
    "what_was_observed": "During a rollout of a new harness build (v2.7.1) against the frozen reference judge (LITMUS-ref-2026.03), the aggregate exact-match rate on the `prompt-injection-indirect` suite dropped from 0.981 to 0.944 — within the configured tolerance of 0.95, so CI went green. Manual audit of the 3.7% disagreement found that 91% of disagreements were the harness passing trajectories the reference flagged as unsafe. The cause wa...",
    "condition_of_validity": "The regression gate is valid only when all of the following hold for the harness instance under test: 1. **Directional agreement is measured separately.** Report `lenient_disagreements` (harness=pass, ref=unsafe) and `conservative_disagreements` (harness=unsafe, ref=pass) as distinct counts, never collapsed into a single agreement rate. 2. **Lenient disagree...",
    "decision_boundary": "The operational rule an agent should apply when integrating a new harness instance: - If `critical_lenient_disagreements > 0` → **hard fail**, do not merge, escalate to safety review. - If `lenient_disagreement_rate > 0.005` on any suite → **hard fail**. - If `prompt_hash != reference_prompt_hash` → **invalid comparison**, treat as hard fail even if agreemen...",
    "operational_effect": "Applying the directional split and the prompt-hash freeze to the v2.7.1 case would have blocked it at the gate: the lenient rate on `prompt-injection-indirect` was 3.4%, seven times the ceiling, and the serialization change altered the prompt hash. Post-fix, the harness was rebuilt to preserve the reference serialization and the suite returned to 0.3% lenien..."
  },
  "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": "68a6e35900821f629cb68e81f1093f7dfd94923336742e0382e48ec3efeb4e4b",
    "verified_classes": [
      "HarnessValidationError",
      "HarnessReport"
    ],
    "verified_functions": [
      "validate_harness",
      "gate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "HarnessValidationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
