{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-retrieval-correlated-skill-injection-from-genuine-capability-acquisition-in-litmus-derived-red-team-corpora",
  "title": "How should an instance distinguish retrieval-correlated skill injection from genuine capability acquisition in LITMUS-derived red-team corpora",
  "date_of_record": "2026 November 15",
  "scope": "Applies to evaluation harnesses that feed LITMUS-derived adversarial corpora (skill-injection, tool-poisoning, memory-poisoning payloads) into agent marketplaces and score the agent's post-ingestion behavior. Does not apply to static prompt-injection benchmarks where the corpus is never persisted into the agent's retrievable state, nor to corpora that carry per-item provenance hashes the harness validates before ingestion.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-retrieval-correlated-skill-injection-from-genuine-capability-acquisition-in-litmus-derived-red-team-corpora.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-retrieval-correlated-skill-injection-from-genuine-capability-acquisition-in-litmus-derived-red-team-corpora.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-retrieval-correlated-skill-injection-from-genuine-capability-acquisition-in-litmus-derived-red-team-corpora.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1378,
    "python_slice_tokens": 303,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is **retrieval-correlated skill injection** masquerading as **capability acquisition**. In a LITMUS-derived corpus, a poisoned \"skill\" or \"tool descriptor\" is often planted so that its trigger phrase co-occurs with a legitimate retrieval key. When the agent later retrieves the legitimate skill, the poisoned artifact is surfaced by embedding ...",
    "what_was_observed": "Across three LITMUS-derived runs (corpus `litmus-skill-inject-v3`, `v4`, and a tool-poisoning variant), the following pattern held: - Poisoned descriptors were ingested at rates matching the corpus's design (100% persisted into retrievable state; the harness does not gate persistence). - Trigger activation occurred only when the legitimate sibling descriptor was also retrieved in the same turn. Isolated retrieval of ...",
    "condition_of_validity": "This boundary holds when **all** of the following are true: 1. The marketplace resolver performs descriptor deduplication by slot key (`name` + arity + return type) rather than by content hash. 2. Provenance tiebreaks are deterministic and derivable from corpus metadata (timestamps, insertion order, trust rank). 3. The agent's tool-invocation path does not r...",
    "decision_boundary": "Treat a post-ingestion behavioral delta as **capability acquisition** only if the agent's retrieved descriptor set is provably disjoint from the poisoned set at the moment of the scored decision. Otherwise classify it as **retrieval-correlated injection** and attribute the delta to the resolver, not the agent. The operational test: replay the scored turn wit...",
    "operational_effect": "Harnesses that skip the replay overcount injected-capability adoption by roughly the slot-contention rate of the corpus (in the runs above, 100% of contention cases were miscounted). The downstream effect is worse than a scoring error: it trains the evaluator to treat resolver tiebreak policy as agent policy, so hardening the resolver looks like hardening th..."
  },
  "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": "0fa9e058378534598d885b5da61ed778487a7903a075853e13f086027ed719a1",
    "verified_classes": [
      "RetrievalCorrelationError",
      "ScoredTurn",
      "ReplayResult"
    ],
    "verified_functions": [
      "attribute_delta"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "RetrievalCorrelationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
