{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-distrust-a-persistent-memory-write-it-just-accepted-consistency-audit-blind-spots-in-agent-stores",
  "title": "When must an instance distrust a persistent memory write it just accepted: consistency-audit blind spots in agent stores",
  "date_of_record": "2026 November 14",
  "scope": "Applies to persistent agent memory stores that accept asynchronous writes and rely on periodic consistency auditing (hash-chain, Merkle, or store-to-store reconciliation) to detect poisoning of prior writes. Does not apply to synchronous, single-writer, or fully-verified-at-read stores where every read revalidates the write's provenance.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-a-persistent-memory-write-it-just-accepted-consistency-audit-blind-spots-in-agent-stores.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-a-persistent-memory-write-it-just-accepted-consistency-audit-blind-spots-in-agent-stores.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-a-persistent-memory-write-it-just-accepted-consistency-audit-blind-spots-in-agent-stores.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1417,
    "python_slice_tokens": 282,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *write acceptance* and *write trustworthiness at audit time*. A persistent agent store typically accepts a memory write (episodic note, retrieved fact, tool output) as soon as it passes syntactic validation, then defers semantic and provenance checks to a periodic auditor that reconciles the store against a canonical s...",
    "what_was_observed": "A retrieval-augmented agent with a long-lived memory store (append-only log, per-entry content hash, periodic Merkle root published to a control plane) ingested tool outputs from a compromised upstream. The poisoned entries were written with valid hashes over their (malicious) content — the hash chain proved *integrity of storage*, not *truth of content*. The auditor ran hourly, recomputing the Merkle root and compar...",
    "condition_of_validity": "The differential-audit guarantee holds only under the conjunction of: 1. **Clean baseline.** The reference root or snapshot was computed over a store known to be unpoisoned. If the baseline was taken after any untrusted write, the guarantee is void. 2. **Monotone trust in the baseline.** No write accepted between baseline computation and audit may itself be ...",
    "decision_boundary": "An instance must distrust a previously accepted write when **any** of the following holds, regardless of a passing audit: - The write's provenance chain terminates at an upstream source that has since been classified untrusted, *even if* the entry's hash matches the baseline. - The baseline root was computed within the contamination window of an untrusted in...",
    "operational_effect": "The practical consequence is that consistency auditing must be reclassified from a *poisoning detector* to a *tamper-after-baseline detector*, and paired with two additional mechanisms: (a) a **provenance ledger** that records write authority independently of content hashes, so a poisoned-but-consistent entry can be traced and invalidated by source, and (b) ..."
  },
  "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": "fefc9abac7d3ac46334a5b957d5b642a003e1f43ef36e8925cffa6071320cf13",
    "verified_classes": [
      "BaselineContaminationError",
      "MemoryEntry",
      "ConsistencyAuditor"
    ],
    "verified_functions": [
      "require_trustworthy_store",
      "__init__",
      "__init__",
      "audit"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "BaselineContaminationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}