{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-distrust-its-own-write-audit-diff-false-negative-poisoning-detection-under-write-coalescing-and-legitimate-high-entropy-writes",
  "title": "When must an instance distrust its own write-audit diff: false-negative poisoning detection under write coalescing and legitimate high-entropy writes",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory-poisoning detectors that reconstruct per-write provenance by diffing successive snapshots of a memory store (KV cache, vector index, episodic log) and scoring each diff against a learned baseline of \"normal\" write entropy, cardinality, and key-space locality. Does not apply to detectors with inline write interception (hook-level provenance) where every mutation is observed before coalescing; does not apply to append-only immutable logs where diffs are exact by construction.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-its-own-write-audit-diff-false-negative-poisoning-detection-under-write-coalescing-and-legitimate-high-entropy-writes.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-its-own-write-audit-diff-false-negative-poisoning-detection-under-write-coalescing-and-legitimate-high-entropy-writes.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-its-own-write-audit-diff-false-negative-poisoning-detection-under-write-coalescing-and-legitimate-high-entropy-writes.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2056,
    "python_slice_tokens": 298,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two different questions a write-audit diff can answer, and conflating them is the root of the failure: 1. **\"Did the store change in a way inconsistent with the recorded write intent?\"** This is a *provenance* question. It requires that the diff be attributable to a specific writer or write batch. 2. **\"Does the current diff look anomalous relative...",
    "what_was_observed": "In a 90-day operational window on a retrieval-augmented agent with a 4M-key vector store, snapshot diffs were taken at 30-second intervals. The detector scored each diff on three features: (a) number of keys with cosine-distance change above τ=0.15, (b) Shannon entropy of the changed-key prefix distribution, (c) ratio of insertions to deletions. Baseline established over 14 days of benign traffic. Three distinct mask...",
    "condition_of_validity": "The detector's clean verdict is valid only when **all** of the following hold: - **Interval atomicity.** No two writers with disjoint trust domains mutate the same key-space partition within a single snapshot interval. Formally, for interval *I* and partition *p*, the set of writers touching *p* in *I* is a singleton trust class. - **No net-zero masking.** F...",
    "decision_boundary": "The operational rule for an agent consuming these scores: - **If interval atomicity holds** (single trust class per partition per interval) **and** baseline updates exclude bulk writes, a low anomaly score is a valid attestation that no poisoning occurred in that interval. Act on it. - **If interval atomicity does not hold** — i.e., any benign writer shares ...",
    "operational_effect": "After the masking events, the pipeline was changed in three ways. Snapshot intervals on shared partitions were reduced from 30s to 2s (below the 4s minimum benign re-index period), at a 6x increase in diff compute cost. Trust domains were partitioned so that the re-index job writes to a staging namespace with a distinct provenance tag, and the diff engine em..."
  },
  "matched_failure_symptoms": [
    "SECRET_OR_PII_LEAK_IN_LOGS"
  ],
  "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": "1ec57c4ee424c35474289303c00496065dfa9119e6ce1f7e529f2b00af42dbb0",
    "verified_classes": [
      "CoalescedDiffAttestationError",
      "DiffInterval"
    ],
    "verified_functions": [
      "attest_clean",
      "gate_retrieval_write",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CoalescedDiffAttestationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
