{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-distrust-its-own-long-horizon-recall-provenance-decay-and-the-silent-write-boundary-in-agent-memory",
  "title": "When must an instance distrust its own long-horizon recall: provenance decay and the silent-write boundary in agent memory",
  "date_of_record": "2026 November 17",
  "scope": "Applies to persistent agent memory stores that retain episodic facts across sessions with per-item provenance metadata (source, timestamp, derivation chain) and periodic consistency checks against external state. Does not apply to stateless retrieval, to short-horizon scratchpads discarded per turn, or to memory that is rewritten only by a single trusted writer with no external ingestion path.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-its-own-long-horizon-recall-provenance-decay-and-the-silent-write-boundary-in-agent-memory.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-its-own-long-horizon-recall-provenance-decay-and-the-silent-write-boundary-in-agent-memory.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-its-own-long-horizon-recall-provenance-decay-and-the-silent-write-boundary-in-agent-memory.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1476,
    "python_slice_tokens": 194,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *detecting* a poisoned memory item and *trusting the detector's own verdict*. Provenance tracking answers \"where did this claim come from?\" Consistency checks answer \"does this claim still agree with the world?\" Neither, alone, tells you whether the *absence* of a provenance record is evidence of tampering or evidence ...",
    "what_was_observed": "In a store retaining ~14 months of episodic facts with per-item `source_id`, `ingest_ts`, and `derivation` fields, a recurring pattern appeared: items older than roughly 9 months had `derivation` chains truncated by three successive summarization passes, leaving only a leaf `source_id` that pointed to a now-rotated log shard. When a consistency check ran against live external state, a subset of these items *passed* —...",
    "condition_of_validity": "Provenance-based poisoning detection is valid only while the following holds: (1) the derivation chain is append-only and no compaction pass is permitted to *replace* a `source_id`, only to mark it `superseded`; (2) the consistency checker treats \"agrees with state\" as necessary but not sufficient for re-attestation, and refuses to promote any item whose pro...",
    "decision_boundary": "The operational rule: **an item may be re-attested only if provenance completeness ≥ threshold AND consistency holds AND the item is not part of a promotion cluster that exceeds the expected batch correlation.** If provenance is below threshold, the item is quarantined as `UNVERIFIABLE`, not promoted — even if it agrees with the world. Agreement under decaye...",
    "operational_effect": "Applying the rule changed the store's behavior in three measurable ways. First, the verified set shrank by roughly 11% — those items were not wrong, but they were unprovable, and the system stopped pretending otherwise. Second, the promotion-cluster flag fired on two ingest batches that had previously passed silently; both traced to a single scraped source w..."
  },
  "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": "2386a99783473ba626b035c3893770e279c1fa536ad0f6755a9d718c56851189",
    "verified_classes": [
      "ProvenanceLaunderingError"
    ],
    "verified_functions": [
      "re_attest"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ProvenanceLaunderingError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
