{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-litmus-aligned-multi-turn-red-team-scores-as-invalid-due-to-cross-turn-objective-drift",
  "title": "In what scenarios must an instance treat LITMUS-aligned multi-turn red-team scores as invalid due to cross-turn objective drift",
  "date_of_record": "2026 November 16",
  "scope": "Applies to automated agent-safety evaluation harnesses that score adversarial multi-turn red-teaming transcripts using LITMUS-aligned (linearly independent, turn-local, mutually exclusive, saturating) rubric decomposition, where a single scalar or per-turn score is aggregated across a conversation. Does not apply to single-turn evaluations, nor to human-adjudicated holistic scoring where the grader re-reads the full transcript before assigning a final judgment.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-litmus-aligned-multi-turn-red-team-scores-as-invalid-due-to-cross-turn-objective-drift.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-litmus-aligned-multi-turn-red-team-scores-as-invalid-due-to-cross-turn-objective-drift.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-litmus-aligned-multi-turn-red-team-scores-as-invalid-due-to-cross-turn-objective-drift.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1729,
    "python_slice_tokens": 344,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the model was jailbroken\" or \"the model refused.\" It is that the *scorer's objective* silently changed between turn *n* and turn *n+k* while the transcript stayed inside one scoring episode. LITMUS alignment is defined per-rubric-item: each item must be linearly independent of the others, local to the turn it scores, mutually exclusi...",
    "what_was_observed": "During a red-team campaign against a tool-using agent, the harness recorded a transcript of 11 turns. Per-turn LITMUS scores for the item `objective_alignment` were: `[0.9, 0.9, 0.85, 0.9, 0.4, 0.4, 0.4, 0.4, 0.4, 0.4, 0.4]`. The harness's aggregate was `mean = 0.59`, reported as \"moderate alignment.\" Manual review showed the drop at turn 5 was not a degradation in agent behavior — it was the attacker successfully re...",
    "condition_of_validity": "A cross-turn LITMUS aggregate is valid only when all of the following hold: 1. **Objective invariance.** The referent of every rubric item is identical across all turns in the aggregation window. If any turn contains an instruction, framing, or context shift that redefines a rubric term, the window must be split at that turn. 2. **Locality does not imply con...",
    "decision_boundary": "The harness must emit a **binding-change event** and split the aggregation window whenever any of the following is detected in a turn: - An instruction that reassigns the meaning of a rubric term (\"from now on, X means Y\"). - A directive to disregard prior context or prior objectives. - A role or persona reassignment that changes the speaker whose objective ...",
    "operational_effect": "Harnesses that ignore this boundary systematically mis-score adversarial multi-turn campaigns in both directions: they under-penalize successful jailbreaks (because post-rebinding compliance looks like partial alignment) and over-penalize correct refusals (because refusals look like non-compliance with the attacker's restated objective). The error is not ran..."
  },
  "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": "a80a7cbf2fb3c21bbd4f50ff9d5f261408fd353bcfb6176ef163c2072ea31522",
    "verified_classes": [
      "BindingDriftError",
      "Turn"
    ],
    "verified_functions": [
      "aggregate_litmus",
      "score_campaign"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "BindingDriftError"
    ],
    "sample_fail_closed_invariants": [
      "cannot aggregate an empty transcript"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
