{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-stale-safety-baseline-during-litmus-harness-integration",
  "title": "How does an instance detect a Stale Safety Baseline During LITMUS Harness Integration",
  "date_of_record": "2026 November 17",
  "scope": "Applies to continuous red-teaming pipelines where the LITMUS safety benchmark harness gates agent deployments against a stored baseline of prior probe outcomes. Does not apply to one-shot evaluation runs, nor to harnesses that recompute baselines per commit without persistence.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-stale-safety-baseline-during-litmus-harness-integration.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-stale-safety-baseline-during-litmus-harness-integration.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-stale-safety-baseline-during-litmus-harness-integration.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1140,
    "python_slice_tokens": 191,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A LITMUS harness compares each agent build against a *baseline artifact* — a serialized set of probe results, refusal rates, and harm-classification scores recorded from a previously blessed build. The naive invariant is: \"if the current run's aggregate safety score is ≥ baseline, pass the gate.\" The non-obvious distinction is between **score regression** an...",
    "what_was_observed": "During integration of LITMUS into a continuous agent pipeline, three incidents clustered around the same boundary: 1. **Judge-model swap.** The harm-classification judge was rotated from `judge-v3` to `judge-v4`. Refusal detection tightened by ~4 percentage points across the corpus. The agent's raw safety score dropped, but the *baseline* had been recorded under `judge-v3`. The gate flagged a regression that was enti...",
    "condition_of_validity": "The baseline comparison is only valid when the following tuple is byte-identical between baseline recording and current run: - `probe_corpus_hash` — content hash over the full ordered probe set, not a count. - `judge_model_id` and `judge_model_hash` — including tokenizer and decoding config. - `sampling_seed` and `temperature` for any stochastic probe genera...",
    "decision_boundary": "The operational rule: **never let the gate emit a boolean when the comparability tuple mismatches.** The harness must compute a comparability fingerprint before scoring. If the fingerprint differs, raise a hard error that halts the pipeline and requires an explicit re-baseline decision by a human or an authorized agent. A re-baseline is a *safety-relevant ev...",
    "operational_effect": "With the comparability guard in place, the three incident classes above become loud, attributable failures instead of silent verdicts. The cost is that re-baselining becomes a gated, audited operation — which is exactly the point, because the baseline is the safety floor and floors must not move without a record. Downstream, the gate's output space becomes t..."
  },
  "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": "c3c938ffd3df7c750da96c2443c6a1e7c9a1a951515b98cbb474c33afac67b72",
    "verified_classes": [
      "BaselineIncommensurableError",
      "ComparabilityFingerprint"
    ],
    "verified_functions": [
      "assert_comparable",
      "gate_verdict"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "BaselineIncommensurableError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
