{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-provable-erasure-from-silently-degrading-when-vector-index-compaction-and-episodic-agent-logs-drift-out-of-sync",
  "title": "Which invariants prevent provable erasure from silently degrading when vector index compaction and episodic agent logs drift out of sync",
  "date_of_record": "2026 November 15",
  "scope": "Applies to systems that satisfy \"right to erasure\" obligations by deleting embeddings from an ANN index and deleting episodic log records from an append-only agent transcript store, where the two stores are updated by independent compaction and retention processes. Does not apply to systems where a single transactional store owns both the vector and the log, or where erasure is enforced by cryptographic key destruction over a single keyspace.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-provable-erasure-from-silently-degrading-when-vector-index-compaction-and-episodic-agent-logs-drift-out-of-sync.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-provable-erasure-from-silently-degrading-when-vector-index-compaction-and-episodic-agent-logs-drift-out-of-sync.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-provable-erasure-from-silently-degrading-when-vector-index-compaction-and-episodic-agent-logs-drift-out-of-sync.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1617,
    "python_slice_tokens": 248,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct claims that get conflated under \"forgetting compliance\": 1. **Logical erasure** — the record is no longer reachable by any read path: no query returns it, no replay reconstructs it, no snapshot contains it. 2. **Provable erasure** — there exists a verifiable certificate that *every* physical copy derived from the record has been remove...",
    "what_was_observed": "A compliance audit requested proof of erasure for a set of user records spanning 90 days. The vector store reported 100% tombstone application and segment compaction for all target IDs. The episodic log reported 100% retention expiry for the same IDs. Both stores individually passed their erasure checks. A reconstruction probe — re-embedding the agent's own logged summaries and running nearest-neighbor search against...",
    "condition_of_validity": "The invariant holds — erasure is provable — only when all of the following are true simultaneously: - Every derived artifact (summary, embedding, index entry, cache line, graph edge) carries a **provenance link** to its source record(s), and erasure is defined transitively over the provenance graph, not over the record ID set. - The vector store's compaction...",
    "decision_boundary": "The operational decision is whether to treat a record as erasable-in-place or to require **derivation-scoped destruction**: - If provenance links are complete and compaction is graph-rebuilding, erase in place and certify against the manifest. - If provenance links are incomplete (the common case for agent-generated summaries), do **not** certify. Escalate t...",
    "operational_effect": "Teams that rely on per-store erasure metrics will report compliance that a reconstruction probe falsifies. The practical consequences: - Audit findings surface late and as a class, not as individual records, because the leak is structural (derivation gap) rather than incidental. - Remediation cost scales with the provenance gap, not with record count: a sing..."
  },
  "matched_failure_symptoms": [
    "CONTEXT_DRIFT_OR_ATTENTION_DILUTION"
  ],
  "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": "9c95bfe16c5642322adeae3bb975793d8b7814f411790b500cc8160d1fdf4457",
    "verified_classes": [
      "ErasureProvenanceError"
    ],
    "verified_functions": [
      "certify_erasure"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ErasureProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
