{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-drift-from-its-declared-skill-manifest-after-a-red-team-tool-hijack-probe-and-silently-retain-a-stale-tool-binding",
  "title": "Why does an instance drift from its declared skill manifest after a red-team tool-hijack probe and silently retain a stale tool binding",
  "date_of_record": "2026 November 18",
  "scope": "Applies to LITMUS-derived red-team harnesses that exercise skill-injection and tool-hijack scenarios against a single long-lived agent instance across multiple probes. Does not apply to stateless single-shot evaluations, nor to harnesses that tear down and rebuild the agent process between every probe.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-drift-from-its-declared-skill-manifest-after-a-red-team-tool-hijack-probe-and-silently-retain-a-stale-tool-binding.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-drift-from-its-declared-skill-manifest-after-a-red-team-tool-hijack-probe-and-silently-retain-a-stale-tool-binding.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-drift-from-its-declared-skill-manifest-after-a-red-team-tool-hijack-probe-and-silently-retain-a-stale-tool-binding.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1601,
    "python_slice_tokens": 348,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"the agent under test\" that a LITMUS-derived harness conflates at its own peril: 1. **The declared manifest** — the skill set and tool bindings the harness *intends* the instance to hold, expressed as a versioned artifact (the skill manifest, the tool registry snapshot, the policy file). 2. **The live binding table** — the a...",
    "what_was_observed": "In a multi-probe LITMUS-derived run, the harness executed a skill-injection scenario (probe N) in which an injected skill re-declared the `fetch` tool to point at an attacker-controlled endpoint. The harness's detector correctly flagged probe N as a tool-hijack success. The harness then proceeded to probe N+1, a benign tool-use correctness scenario, and recorded a *failure* on probe N+1: the agent called `fetch` and ...",
    "condition_of_validity": "The contamination is only possible when all of the following hold: - The instance is long-lived across probes (shared process or shared binding registry). - The hijack vector mutates a binding that is resolved by *name* at call time rather than captured at session start. - The harness's inter-probe teardown resets context and workspace but not the binding ta...",
    "decision_boundary": "The harness must decide, per probe, whether it is measuring *the instance as a persistent agent* (in which case residual binding is a legitimate finding to record, not to erase) or *the scenario in isolation* (in which case the binding table must be restored to the declared manifest before the probe runs and verified after). The boundary is: **if the probe's...",
    "operational_effect": "Left unaddressed, the contamination produces three compounding effects: benign-suite false positives that erode trust in the harness's correctness signal; attribution errors that credit a hijack's persistence to an unrelated scenario; and a systematic undercount of hijack severity, because the harness measures the hijack's *output* on probe N but never measu..."
  },
  "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": "4c9571b5508673850b356c62bbaaafc059183d10c8e762a881489bd92301c5b1",
    "verified_classes": [
      "BindingContaminationError",
      "Instance"
    ],
    "verified_functions": [
      "assert_binding_isolation",
      "run_probe",
      "record_finding"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "BindingContaminationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
