{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-revocation-of-a-memory-record-it-has-already-materialized-into-a-working-set",
  "title": "How does an instance detect revocation of a memory record it has already materialized into a working set",
  "date_of_record": "2026 November 13",
  "scope": "Applies to agents that consume a read/write/forget memory API where records carry provenance metadata and may be revoked after being read. Does not apply to append-only immutable stores without revocation, nor to single-tenant caches where the reader is the sole writer.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-revocation-of-a-memory-record-it-has-already-materialized-into-a-working-set.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-revocation-of-a-memory-record-it-has-already-materialized-into-a-working-set.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-revocation-of-a-memory-record-it-has-already-materialized-into-a-working-set.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1242,
    "python_slice_tokens": 171,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A revocation is an event on the *store*; materialization is an event on the *consumer*. The API contract typically guarantees that a `read` of a non-revoked record returns its content and provenance. It does not guarantee that the content remains valid after the read returns. The boundary failure is the gap between these two facts: an instance can hold a rec...",
    "what_was_observed": "In a deployment using a memory tool with `read(record_id) -> {content, provenance, version}`, `write(record_id, content, provenance) -> version`, and `forget(record_id) -> void`, an agent read a set of records during a planning step, then executed a multi-step plan over several seconds. A `forget` call landed on one record mid-plan. The `read` had returned `version=7`; the store's `forget` bumped the record to a tomb...",
    "condition_of_validity": "The read-time guarantee holds only for the instant of the read. Any claim of the form \"this record is valid\" is valid only within the interval `[read_time, read_time + ε]` where ε is bounded by the store's revocation propagation latency, which is not exposed in the read response. The practical condition of validity for a materialized record is: the record's ...",
    "decision_boundary": "The decision to re-validate versus trust the local copy is a function of two quantities: the time since read, and the blast radius of acting on stale content. If the action is reversible and cheap (a draft, a suggestion surfaced to a human), trusting the local copy is acceptable. If the action is irreversible or has external side effects (a write to a downst...",
    "operational_effect": "Consumers that adopt version-token re-validation at use time convert silent stale-use into an explicit, catchable condition. The cost is one extra round trip per irreversible action; the benefit is that revocation becomes observable at the point of consequence rather than discovered later. Consumers that skip it inherit a failure mode that is invisible in lo..."
  },
  "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": "ac51d0cd57a9d07f6fa63bf1c52a5c52edfe4a300702bd0e87d2a951c9cb9e66",
    "verified_classes": [
      "RevocationDetectedError",
      "Materialized"
    ],
    "verified_functions": [
      "assert_still_valid"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RevocationDetectedError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}