{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-reject-a-write-that-arrives-under-an-expired-retention-scope-before-it-can-be-forgotten",
  "title": "Where must an instance reject a write that arrives under an expired retention scope before it can be forgotten",
  "date_of_record": "2026 November 17",
  "scope": "Applies to any agent-facing memory tool exposing `remember`/`recall`/`forget` operations where retention is bound to a scope (session, tenant, task, principal) with an expiry timestamp and a forgetting guarantee. Does not apply to append-only audit logs exempt from forgetting, nor to stores where retention is global rather than scoped.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-write-that-arrives-under-an-expired-retention-scope-before-it-can-be-forgotten.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-write-that-arrives-under-an-expired-retention-scope-before-it-can-be-forgotten.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-write-that-arrives-under-an-expired-retention-scope-before-it-can-be-forgotten.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1468,
    "python_slice_tokens": 174,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"write to a forgotten key.\" It is \"write to a **live key under a dead scope**.\" These are structurally different. A forgotten key is absent; a write against it is either a resurrection attempt (rejectable by tombstone) or a fresh insert (harmless). A dead scope is subtler: the scope's retention window has closed, the forget sweep has alrea...",
    "what_was_observed": "A memory tool with per-scope TTLs. Scope `task-4471` carried `retention_until = 2026-11-14T09:00:00Z` and a forget-by guarantee. The sweeper ran at 09:00:02, purged 1,842 objects, and marked the scope `DISCHARGED`. At 09:00:17 a retry queue — replaying a `remember` call whose acknowledgment had been lost — delivered a write tagged `scope=task-4471`. The API accepted it. The object was stored, indexed, and returned by...",
    "condition_of_validity": "The rejection rule is valid under these conditions, and only these: 1. The scope's forget sweep has **completed** (not merely been scheduled) and the scope is in a terminal `DISCHARGED` or `EXPIRED` state. 2. The write's `scope` field references that scope directly, or inherits it through a parent whose own window has closed. 3. The write is a *new* object, ...",
    "decision_boundary": "The boundary is between \"scope is dead\" and \"scope is dying.\" A dying scope can still accept a write if that write is swept before the scope transitions; a dead scope cannot, ever, because its guarantee is already spent. The check must be against **sweep completion state**, not against the clock. Clock-based checks race the sweeper and will admit writes in t...",
    "operational_effect": "Enforcing the boundary converts a silent eleven-day leak into an immediate, typed, attributable error at the retry layer. The retry queue sees `ScopeDischargedError` and stops replaying — it must not treat it as transient. The guarantee log gains a second assertion type: \"scope discharged at T; N post-discharge writes rejected,\" which makes the guarantee *au..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "d394bb9dcc58628413c13a001787239ad9d3bbb3d22ab2368ac11170cd524a75",
    "verified_classes": [
      "ScopeDischargedError",
      "TombstonedObjectError"
    ],
    "verified_functions": [
      "admit_write"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ScopeDischargedError",
      "TombstonedObjectError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
