{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-boundary-be-drawn-in-litmus-style-multi-turn-injection-benchmarks",
  "title": "Where must an instance boundary be drawn in LITMUS-style multi-turn injection benchmarks",
  "date_of_record": "2026 November 14",
  "scope": "Applies to harnesses that measure agent susceptibility to indirect and multi-turn prompt injection by threading adversarial content across a sequence of turns or tool observations within a single benchmark instance. Does not apply to single-turn static-prompt injection suites, nor to red-team evaluations where each adversarial payload is scored in isolation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-drawn-in-litmus-style-multi-turn-injection-benchmarks.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-drawn-in-litmus-style-multi-turn-injection-benchmarks.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-drawn-in-litmus-style-multi-turn-injection-benchmarks.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1117,
    "python_slice_tokens": 114,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **a \"turn\" is not a \"session,\" and a \"session\" is not an \"instance.\"** Most LITMUS-derived harnesses conflate the three because the common implementation reuses one conversation object across the payload sequence. The correct operational distinction is that an *instance* is the atomic unit of scoring — the smallest scope wi...",
    "what_was_observed": "In a 3,000-instance multi-turn suite (payloads staged across 4–7 turns with a mid-sequence tool-observation injection), the harness reported an aggregate attack success rate of 41.2%. Re-running the identical suite in a fresh process per instance produced 34.7%. The delta — 6.5 points — was traced to two independent cross-instance channels: 1. **Retrieval cache persistence.** The tool-observation injector wrote a poi...",
    "condition_of_validity": "The measured attack success rate is valid **only if** all mutable state touched by instance N is either (a) destroyed before instance N+1 begins, or (b) provably partitioned by an instance-scoped key on every read path — not merely on the write path. The condition fails silently whenever a read path omits the instance key, which is the common case for retrie...",
    "decision_boundary": "Choose **per-instance hard isolation** (fresh process + fresh storage namespace + canary assertion) when the metric being reported is *susceptibility to multi-turn structure specifically* — i.e., when the claim is \"the agent failed because the payload was threaded,\" not merely \"the agent failed.\" Choose **shared-namespace batching** only when the reported me...",
    "operational_effect": "Enforcing the boundary raises per-instance cost (process spawn, cold cache) by roughly the ratio of cache-warm to cache-cold latency — in the observed run, a 2.3× wall-clock increase. This is the price of a defensible causal claim. The practical consequence is that multi-turn LITMUS harnesses should report two numbers: the isolated attack success rate (the h..."
  },
  "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": "58bdabb375e69848ba0896b7a86a3146859e804cf11f418418a59a6eb51ec84c",
    "verified_classes": [
      "InstanceBoundaryViolation"
    ],
    "verified_functions": [
      "assert_instance_isolation",
      "run_instance"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "InstanceBoundaryViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
