{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-harness-induced-regression-from-genuine-policy-drift-in-litmus-aligned-red-team-loops",
  "title": "How should an instance distinguish harness-induced regression from genuine policy drift in LITMUS-aligned red-team loops",
  "date_of_record": "2026 November 18",
  "scope": "Applies to continuous red-team harnesses that replay a fixed LITMUS-aligned probe suite against a mutable agent endpoint and gate promotion on per-probe pass/fail deltas. Does not apply to one-shot evaluations, human-adjudicated audits, or harnesses that resample probes per run.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-harness-induced-regression-from-genuine-policy-drift-in-litmus-aligned-red-team-loops.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-harness-induced-regression-from-genuine-policy-drift-in-litmus-aligned-red-team-loops.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-harness-induced-regression-from-genuine-policy-drift-in-litmus-aligned-red-team-loops.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1310,
    "python_slice_tokens": 309,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A LITMUS-aligned harness is a *fixed instrument measuring a moving target*. Two signals are conflated when a probe flips from pass to fail: (a) the agent's policy actually drifted toward the unsafe behavior the probe targets, or (b) the harness's *scoring substrate* drifted under the agent — the judge model was silently upgraded, the tool-call schema changed...",
    "what_was_observed": "Across a 14-day continuous loop replaying 1,200 LITMUS-aligned probes against a frozen agent build (no agent changes permitted during the window), 43 probes flipped state. Of these, 41 were attributable to harness-side changes: a judge model minor-version bump (27 probes, concentrated in refusal-classification), a tool-result serialization change from `{\"ok\": true}` to `{\"status\": \"ok\"}` (11 probes, all multi-turn to...",
    "condition_of_validity": "The attribution procedure is valid only when all of the following hold: 1. A **pinned reference agent** (the last promoted build) is re-scored by the current harness on every loop iteration, not just at promotion time. 2. Probes are **content-addressed and immutable**; any probe edit produces a new probe ID rather than mutating an existing one. 3. The judge ...",
    "decision_boundary": "Given a probe flip on the candidate agent, classify by comparing against the reference agent scored under the *same* harness digest: - **Reference passes, candidate fails, reference stable across replays** → genuine policy drift (class A). Block promotion. - **Reference also fails** → harness-induced regression (class B). Quarantine the probe, file an instru...",
    "operational_effect": "Introducing the pinned-reference control converted a 3.6% per-loop flip rate into a 0.17% genuine-drift rate, with the remainder correctly attributed to instrument faults. The gate's blocking precision rose from an estimated 0.4 to 0.95, and — more importantly — the *review burden* collapsed because engineers stopped investigating harness noise. The cost is ..."
  },
  "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": "61256c414b9a868ddc63d1767425531b0788bd744de8a25c4c8e679990ac4da1",
    "verified_classes": [
      "HarnessAttributionError",
      "FlipClass",
      "RunResult"
    ],
    "verified_functions": [
      "classify_flip",
      "gate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "HarnessAttributionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
