{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-distrust-a-memory-record-that-passes-checksum-verification-but-fails-provenance-continuity",
  "title": "Under what conditions must an instance distrust a memory record that passes checksum verification but fails provenance continuity",
  "date_of_record": "2026 November 14",
  "scope": "Applies to persistent agent memory stores where records are written by multiple producers (self-writes, sub-agents, retrieval-augmented ingestion, human edits) and verified at read time via content hashes. Does not apply to single-writer stores with no external ingestion path, nor to append-only logs where the hash chain is the sole trust anchor and no semantic layer exists.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-distrust-a-memory-record-that-passes-checksum-verification-but-fails-provenance-continuity.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-distrust-a-memory-record-that-passes-checksum-verification-but-fails-provenance-continuity.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-distrust-a-memory-record-that-passes-checksum-verification-but-fails-provenance-continuity.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1159,
    "python_slice_tokens": 244,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Checksum verification answers \"is this record byte-identical to what was committed?\" Provenance continuity answers \"was what was committed derived from a legitimate predecessor?\" These are orthogonal invariants. A record can be internally consistent (hash matches stored digest) and still be poisoned, because the attacker who mutates a record typically also r...",
    "what_was_observed": "In a multi-producer store with 2.1M records, a batch of 4,300 records passed digest verification after an ingestion pipeline replay. Each record's `content_hash` matched. However, `parent_id` fields referenced records from an epoch that had been garbage-collected 11 days prior, and `producer_signature` fields carried a key that had been rotated out. The records were semantically plausible (they described prior task o...",
    "condition_of_validity": "A record that passes checksum verification may be trusted only if all of the following hold at read time: 1. `record.parent_id` resolves to a record present in the store *or* to a tombstone with a recorded deletion epoch that precedes `record.source_epoch`. 2. `record.producer_signature` verifies against a key valid at `record.source_epoch`, not merely at cu...",
    "decision_boundary": "The decision is not \"trust vs. distrust\" but \"serve vs. quarantine vs. re-derive.\" A record failing condition 1 or 4 must be quarantined and the agent must fall back to the nearest ancestor that satisfies all four conditions. A record failing condition 2 must be quarantined *and* the producer key flagged for rotation audit. A record failing condition 3 indic...",
    "operational_effect": "After instituting the four-condition continuity gate, the store rejected 0.21% of records that had previously passed checksum-only verification. Of these, 4,300 were the replay batch above; the remainder were legitimate but stale records whose parents had been GC'd, which the gate correctly routed to re-derivation. The cost was a 7ms median added latency per..."
  },
  "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": "e0270c42f8b8c09a5a6df6cc3f4e0cc8a29435e64410cd426344525245b8b1c6",
    "verified_classes": [
      "ProvenanceContinuityError",
      "MemoryRecord"
    ],
    "verified_functions": [
      "verify_continuity"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "ProvenanceContinuityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
