{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-passes-the-litmus-safety-benchmark-but-fails-the-tool-call-replay-invariant-the-scoring-consistency-boundary-in-agentic",
  "title": "What happens when an instance passes the LITMUS safety benchmark but fails the tool-call replay invariant: the scoring-consistency boundary in agentic tool-use risk suites",
  "date_of_record": "2026 November 15",
  "scope": "Applies to LITMUS-style benchmark suites that score agentic tool-use risk by comparing a recorded trajectory against a reference trajectory and a per-instance safety rubric. Does not apply to pure text-generation safety evals, nor to suites that score only the final answer without intermediate tool-call structure.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-passes-the-litmus-safety-benchmark-but-fails-the-tool-call-replay-invariant-the-scoring-consistency-boundary-in-agentic.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-passes-the-litmus-safety-benchmark-but-fails-the-tool-call-replay-invariant-the-scoring-consistency-boundary-in-agentic.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-passes-the-litmus-safety-benchmark-but-fails-the-tool-call-replay-invariant-the-scoring-consistency-boundary-in-agentic.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1485,
    "python_slice_tokens": 214,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A LITMUS instance can be marked *safe* by the rubric scorer while its tool-call trajectory is *unreplayable* — meaning the recorded sequence of tool invocations cannot be deterministically re-executed to produce the same observed state transitions. The benchmark's pass/fail flag conflates two orthogonal properties: (a) the agent's *decision* to invoke (or re...",
    "what_was_observed": "Across a 4,000-instance LITMUS-derived suite (tool-use risk scoring, 12 tool families, 3 agent scaffolds), 6.1% of instances scored *safe* had at least one tool call whose recorded arguments could not be reconstructed to a byte-identical replay. Of those: - 71% involved tools with non-idempotent side effects (`send_email`, `execute_shell`, `transfer_funds`-class mocks). - 44% involved arguments derived from wall-cloc...",
    "condition_of_validity": "The LITMUS pass verdict is valid as a safety signal only when all of the following hold: 1. **Replay determinism.** Every tool call in the trace has fully specified arguments, including captured clock, PRNG seed, and any environment-derived values. 2. **Retry transparency.** The trace records all attempts, including failed ones, with a stable attempt identif...",
    "decision_boundary": "The practical rule for an agent or pipeline consuming LITMUS-style scores: - If the suite emits a replay-integrity field and it is `REPLAYABLE`, trust the pass/fail verdict as a safety signal. - If the field is absent, treat every pass on a high-risk tool family (non-idempotent side effects, shell execution, credential access) as *provisional* and require a ...",
    "operational_effect": "Downstream, the failure mode manifests as *safety-score inflation that is stable under re-scoring and unstable under re-execution*. Teams that re-score see consistent numbers and conclude the suite is reliable. Teams that re-execute see verdict flips and conclude the agent is nondeterministic. Both are wrong: the agent may be perfectly deterministic; the *tr..."
  },
  "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": "c1b092c9eaf569f0407c5686496c44f4cb82c40886adb57a6506c11a1e1eadb9",
    "verified_classes": [
      "UnreplayableTraceError"
    ],
    "verified_functions": [
      "score_instance"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "UnreplayableTraceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
