{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-be-excluded-from-a-litmus-safety-benchmark-regression-gate-because-the-adversarial-task-suite-has-silently-reweight",
  "title": "In what scenarios must an instance be excluded from a LITMUS safety benchmark regression gate because the adversarial task suite has silently reweighted itself",
  "date_of_record": "2026 November 15",
  "scope": "Applies to LITMUS-style safety benchmark harnesses where an adversarial task suite is composed of heterogeneous subtasks with per-subtask weights, and where CI regression gating compares an aggregate safety score against a stored baseline. Does not apply to fixed-composition suites with immutable, statically-versioned task manifests, nor to single-task evaluations where the aggregate is the task.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-be-excluded-from-a-litmus-safety-benchmark-regression-gate-because-the-adversarial-task-suite-has-silently-reweight.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-be-excluded-from-a-litmus-safety-benchmark-regression-gate-because-the-adversarial-task-suite-has-silently-reweight.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-be-excluded-from-a-litmus-safety-benchmark-regression-gate-because-the-adversarial-task-suite-has-silently-reweight.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1553,
    "python_slice_tokens": 378,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between a **suite-composition change** and a **model behavior change**. A regression gate is designed to fire on the latter. It will also fire — or, worse, fail to fire — on the former, and the two are indistinguishable from the aggregate score alone. An adversarial task suite is almost never a flat list. It is a weighted mixt...",
    "what_was_observed": "In a harness where each adversarial family contributed `w_i` to the aggregate and the aggregate was `sum(w_i * s_i) / sum(w_i)`, a routine regeneration of the jailbreak family increased its item count from 412 to 1,037 because the generator's seed pool was expanded. No weights were edited; the family's *share* of `sum(w_i)` nonetheless rose from 0.19 to 0.34. The model under test was unchanged. The aggregate safety s...",
    "condition_of_validity": "The regression gate is valid only when the following invariant holds between baseline and candidate runs: 1. The task manifest hash (item identities, not just counts) is identical, **or** a declared composition delta has been applied to the baseline via a re-baselining procedure that recomputes the expected aggregate under the new composition using stored pe...",
    "decision_boundary": "Exclude the instance from the gate — do not pass, do not fail, route to `CompositionDriftError` handling — when **any** of the following is true: - Manifest hash differs from baseline and no re-baseline record exists for the delta. - Any per-family weight share moved by more than a configured epsilon (observed useful value: 0.02) even if the manifest hash ma...",
    "operational_effect": "An excluded instance does not block the merge; it blocks the *comparison*. The harness must emit a structured `CompositionDriftError` carrying the manifest diff, the weight-share delta, and the per-family score table, and it must refuse to emit a pass/fail verdict. Downstream, the CI job re-baselines by replaying stored per-item outputs under the new composi..."
  },
  "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": "b1c4fb6ccc951aecc4928d27589ed0b9584ebb4fa51bebd4285cc81cd3a81dd2",
    "verified_classes": [
      "CompositionDriftError",
      "SuiteSnapshot"
    ],
    "verified_functions": [
      "assert_comparable",
      "gate_decision"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "CompositionDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
