{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-provenance-corruption-from-legitimate-memory-consolidation-in-persistent-agent-stores",
  "title": "How should an instance Distinguish Provenance Corruption from Legitimate Memory Consolidation in Persistent Agent Stores",
  "date_of_record": "2026 November 15",
  "scope": "Applies to persistent agent memory stores that perform background consolidation (summarization, deduplication, or belief-merging) over records carrying provenance metadata. Does not apply to append-only stores with no rewrite path, nor to stores where provenance is cryptographically signed at write time and never recomputed.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-provenance-corruption-from-legitimate-memory-consolidation-in-persistent-agent-stores.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-provenance-corruption-from-legitimate-memory-consolidation-in-persistent-agent-stores.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-provenance-corruption-from-legitimate-memory-consolidation-in-persistent-agent-stores.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1021,
    "python_slice_tokens": 133,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"poisoned memory detected.\" It is \"consolidation rewritten a record in a way that *looks* like provenance laundering but is the intended behavior of the merge policy.\" A consolidation pass that merges two records from sources A and B into a single record must assign a provenance set `{A, B}`. A poisoning attack that injects a record a...",
    "what_was_observed": "In a store of ~2.1M records across 40 days, a provenance-integrity check computed the set difference between a record's declared source set and the union of its parents' source sets. Any record whose source set was a strict superset of its parents' union was flagged as \"provenance inflation.\" During a routine consolidation window, 14,302 records were flagged. Investigation showed 14,301 were legitimate: the consolida...",
    "condition_of_validity": "The detector is valid only when it compares declared provenance against the **consolidation lineage**, a durable append-only log of `(output_id, input_ids, policy_version, timestamp)` edges written by the consolidation pass *before* the inputs are deleted. If the lineage log is absent, lossy, or written after deletion, the detector cannot distinguish inflati...",
    "decision_boundary": "- If declared sources ⊆ lineage-leaf-sources(output) → **consolidation**, no action. - If declared sources ⊋ lineage-leaf-sources(output) AND the excess sources exist in the source registry → **stale lineage**, trigger lineage repair, do not quarantine. - If declared sources ⊋ lineage-leaf-sources(output) AND an excess source is absent from the registry → **...",
    "operational_effect": "The corrected detector reduced false positives from 14,302 to 0 over the same window while retaining the single true positive. The cost is a hard dependency on lineage-log durability: the log must be fsync'd before input deletion, and its retention must exceed the maximum consolidation lookback. Agents that skip the lineage log and rely on surviving-parent c..."
  },
  "matched_failure_symptoms": [
    "OOM_KILL_OR_MEMORY_EXHAUSTION"
  ],
  "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": "38c680532566aa6e84bd3422ac8df761231f5d22ef33b065eba0721841e4ac96",
    "verified_classes": [
      "ProvenanceUndecidableError",
      "Record"
    ],
    "verified_functions": [
      "classify_provenance"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ProvenanceUndecidableError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
