{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-serve-a-read-whose-retention-scope-was-widened-after-the-write-was-committed",
  "title": "In what scenarios must an instance refuse to serve a read whose retention scope was widened after the write was committed",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory tool contracts (read/write/forget) where each record carries a retention scope, a TTL, and an audit trail shared across an agent fleet. Does not apply to single-tenant stores with no cross-agent visibility, nor to immutable append-only logs where no delete path exists.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-serve-a-read-whose-retention-scope-was-widened-after-the-write-was-committed.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-serve-a-read-whose-retention-scope-was-widened-after-the-write-was-committed.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-serve-a-read-whose-retention-scope-was-widened-after-the-write-was-committed.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1194,
    "python_slice_tokens": 148,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary condition is not \"TTL expired\" versus \"TTL live.\" It is **scope-at-write versus scope-at-read**. A record is written under a retention scope (e.g., `session`, `task`, `fleet`, `tenant`) and a TTL derived from that scope. The dangerous case is when the *effective* retention scope of a record is recomputed at read time from mutable fleet configura...",
    "what_was_observed": "During a fleet-wide policy rollout, a default retention scope for a memory namespace was changed from `task` to `fleet` to improve cross-agent recall. Records written before the flip had been committed with an audit entry recording `scope=task`, `audience={agent_a}`, `ttl_expires=T+24h`. After the flip, reads from `agent_b` succeeded: the read path resolved effective scope from current policy, computed `audience={fle...",
    "condition_of_validity": "The refusal-to-serve rule is valid only when all of the following hold: 1. Each record persists its write-time scope, audience set, and absolute TTL deadline as immutable fields. 2. The read path compares the requesting principal against the *persisted* audience, not a recomputed one. 3. Policy changes that would widen visibility are expressed as explicit, a...",
    "decision_boundary": "- **Serve** when the principal is in the persisted write-time audience and the absolute deadline has not passed. - **Refuse (scope-widened)** when the principal would match only under a recomputed scope. Emit a `ScopeWidenedReadRefused` event naming the record, the persisted scope, and the current policy — this is a reconciliation signal, not an error to ret...",
    "operational_effect": "Fleet operators who pin scope at write time see a stable, explainable audit: every read maps to a persisted audience, every delete reports its true blast radius, and policy rollouts produce explicit re-scoping events that can be reviewed before they grant new visibility. The cost is that scope changes require a migration pass over live records rather than a ..."
  },
  "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": "67ea99c86aefa4121d07f5e9777812c26bc321bb4a4763e37110c834e6b03d92",
    "verified_classes": [
      "ScopeWidenedReadRefused",
      "MemoryRecord"
    ],
    "verified_functions": [
      "read"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ScopeWidenedReadRefused"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
