{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-forgets-a-memory-that-is-still-referenced-by-a-provenance-chain",
  "title": "What happens when an instance forgets a memory that is still referenced by a provenance chain",
  "date_of_record": "2026 November 16",
  "scope": "Applies to read/write/forget memory tool APIs that combine scoped eviction, TTL-based expiration, and provenance-tracked recall, where a recalled memory may cite or depend on other memory records. Does not apply to single-record CRUD stores without cross-record references, nor to append-only logs where no record is ever evicted.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-forgets-a-memory-that-is-still-referenced-by-a-provenance-chain.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-forgets-a-memory-that-is-still-referenced-by-a-provenance-chain.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-forgets-a-memory-that-is-still-referenced-by-a-provenance-chain.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1548,
    "python_slice_tokens": 322,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The critical distinction is between *eviction as a visibility operation* and *eviction as a referential operation*. In a scoped-eviction API, `forget(scope=...)` removes records from the readable set of a scope. This is a visibility change: the record is no longer returned by `recall()`. It is **not** a referential integrity operation. A provenance chain is ...",
    "what_was_observed": "An agent operating over a scoped memory store performed the following sequence within a single session: 1. Wrote memory `A` (scope `tenant:acme`, TTL 3600s): \"Q3 revenue figure is 4.2M, source: finance_export_0912.\" 2. Wrote memory `B` (scope `tenant:acme`, no TTL): \"Board summary claims YoY growth of 12%, derived_from A.\" 3. At T+3700s, `A` expired via TTL and was hard-evicted. `B` remained because its scope had no ...",
    "condition_of_validity": "The invariant that must hold is: *a record is recallable with `confidence > degraded` only if every record in its transitive `derived_from` closure is currently live within an intersecting scope.* This holds only when the memory API performs closure validation at read time. It does **not** hold—and must not be assumed—when: - Eviction is scoped such that a d...",
    "decision_boundary": "The operational decision is what to do at the moment of eviction and at the moment of recall. The boundary is drawn as follows: - **On eviction of A:** if `A` has live dependents, the store must either (a) cascade-evict dependents, (b) mark dependents `degraded` and stamp them with the eviction event, or (c) refuse the eviction and surface the dependency. Si...",
    "operational_effect": "After the defect was identified, the store was changed to maintain a reverse dependency index and to validate provenance closure on every `recall()` that returns a record with non-empty `derived_from`. Recall of `B` after `A`'s expiry now returns `B` with `provenance_status: broken`, `confidence: low`, and an `evicted_antecedents: [\"A\"]` field. TTL for deriv..."
  },
  "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": "6b82324a22f3446fb831a0c11d916c62bc576e381681b2d0e88d99893ed3aac3",
    "verified_classes": [
      "BrokenProvenanceError",
      "MemoryRecord",
      "ScopedMemoryStore"
    ],
    "verified_functions": [
      "__init__",
      "write",
      "forget",
      "_closure_broken",
      "recall"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "BrokenProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
