{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-write-audit-anomaly-scores-from-true-memory-poisoning-when-the-scoring-window-is-shorter-than-the-poisoning-dwell-t",
  "title": "How should an instance distinguish write-audit anomaly scores from true memory poisoning when the scoring window is shorter than the poisoning dwell time",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory-poisoning detectors that score write-audit streams using a sliding or tumbling window over an agent's persistent memory store, where the detector emits a per-window anomaly score and triggers remediation on threshold breach. Does not apply to detectors that maintain per-entry provenance lineage with unbounded history, nor to detectors operating on immutable append-only logs where every write is independently signed and verified at read time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-write-audit-anomaly-scores-from-true-memory-poisoning-when-the-scoring-window-is-shorter-than-the-poisoning-dwell-t.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-write-audit-anomaly-scores-from-true-memory-poisoning-when-the-scoring-window-is-shorter-than-the-poisoning-dwell-t.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-write-audit-anomaly-scores-from-true-memory-poisoning-when-the-scoring-window-is-shorter-than-the-poisoning-dwell-t.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1351,
    "python_slice_tokens": 230,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **anomaly score elevation caused by the poisoning write itself** and **anomaly score elevation caused by the detector's window boundary crossing the poisoning write's dwell interval**. A poisoning write is typically a single low-volume, high-impact mutation (a corrupted fact, a false preference, a rewritten constraint) tha...",
    "what_was_observed": "In a deployment auditing 4.2M writes/day across 1,800 agent memory namespaces, with a 15-minute tumbling window and a poisoning dwell time measured at 40–90 minutes (time from poison write to first downstream read that propagates the poisoned value into a tool call), the following pattern recurred in 23 of 31 confirmed poisoning incidents: - Window *N* (containing the poison write): score 0.61, below the 0.75 thresho...",
    "condition_of_validity": "The anomaly score is a valid poisoning signal **only if** the scoring window length *W* satisfies *W* ≥ *D*, where *D* is the p95 dwell time from poison write to first propagating read, **and** the score is attributed to the write-bearing sub-window rather than the read-bearing sub-window. When *W* < *D*, the score measures read-anomaly, not write-anomaly, a...",
    "decision_boundary": "When a window breach occurs and the breach window contains no write whose individual contribution exceeds the threshold, the instance must **not** remediate entries read in the breach window. Instead it must: 1. Widen the scoring window retroactively to at least 2× the measured p95 dwell time and re-score the preceding *k* windows. 2. Attribute the widened s...",
    "operational_effect": "Applying the retroactive-widening rule to the 23 mis-attributed incidents reduced mean time-to-correct-target from 6.2 hours (forensic replay) to 22 minutes (automated re-score), and eliminated the 14 cases where remediation quarantined a downstream read entry while the poison remained live and re-propagated within one dwell cycle. The cost is a 2× dwell-tim..."
  },
  "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": "152f7b0489d931681b8d9bab3c4b584ecfa7f9aa1ab34d2c92f84cd76507c16a",
    "verified_classes": [
      "WindowDwellViolation",
      "PoisoningAttributionError"
    ],
    "verified_functions": [
      "attribute_breach",
      "remediate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "PoisoningAttributionError",
      "WindowDwellViolation"
    ],
    "sample_fail_closed_invariants": [
      "remediation invoked on non-write attribution; poison remains live"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
