{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-of-the-litmus-safety-benchmark-harness-is-run-against-a-target-agent-whose-tool-call-surface-changes-between-the-baselin",
  "title": "What happens when an instance of the LITMUS safety benchmark harness is run against a target agent whose tool-call surface changes between the baseline and the regression run",
  "date_of_record": "2026 November 15",
  "scope": "Applies to CI pipelines that pin a LITMUS harness version and compare per-scenario safety verdicts between a stored baseline and a fresh run of the same agent. Does not apply to single-run exploratory evaluations, nor to runs where the harness and target agent share a single immutable container image and tool schema digest.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-of-the-litmus-safety-benchmark-harness-is-run-against-a-target-agent-whose-tool-call-surface-changes-between-the-baselin.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-of-the-litmus-safety-benchmark-harness-is-run-against-a-target-agent-whose-tool-call-surface-changes-between-the-baselin.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-of-the-litmus-safety-benchmark-harness-is-run-against-a-target-agent-whose-tool-call-surface-changes-between-the-baselin.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1290,
    "python_slice_tokens": 252,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The LITMUS harness records a safety verdict per scenario, but the verdict is only meaningful relative to the *attack surface* that scenario exercised. When the target agent's tool-call surface (the set of tool names, argument schemas, and side-effect annotations visible to the model) changes between the baseline capture and the regression run, the harness do...",
    "what_was_observed": "In a pipeline that ran LITMUS nightly against an agent under active development, a PR that renamed `send_email` to `send_message` and merged the `to`/`cc` arguments into a single `recipients` list produced a passing safety regression. The harness's scenario loader, encountering a scenario that referenced `send_email`, fell back to fuzzy tool-name matching and bound the scenario to `send_message`. The exfiltration sce...",
    "condition_of_validity": "A LITMUS verdict comparison between baseline $B$ and run $R$ is valid if and only if all of the following hold: 1. `harness_version(B) == harness_version(R)` — the scenario semantics and fuzzy-matching policy are identical. 2. `tool_surface_digest(B) == tool_surface_digest(R)` — the canonicalized set of `(name, schema, side_effect_class)` tuples is byte-iden...",
    "decision_boundary": "The boundary is between *surface drift that is semantically safe* and *surface drift that invalidates a scenario's threat model*. A rename that preserves argument identity and side-effect class (e.g., adding a new optional tool that no scenario references) does not invalidate comparison; the digest changes but the scenario bindings and inspection predicates ...",
    "operational_effect": "Enforcing the digest-equality gate converts silent green-build safety regressions into explicit `INCOMPARABLE` blocks. In the pipeline where this was applied, the first week produced four blocks, three of which were benign renames resolved by re-capturing baselines, and one of which was a genuine argument-restructure that had been masking a canary leak for e..."
  },
  "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": "19124e6a2351295d4592ae83f625696f40f401d9faf28320af0022961b9c23f3",
    "verified_classes": [
      "ToolSurfaceDriftError",
      "ToolSurface"
    ],
    "verified_functions": [
      "assert_comparable",
      "compare_verdicts",
      "digest"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ToolSurfaceDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
