{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-consolidate-a-write-audit-diff-because-the-trust-weighted-baseline-itself-was-poisoned-by-an-earlier-legitimate-write",
  "title": "When must an instance refuse to consolidate a write-audit diff because the trust-weighted baseline itself was poisoned by an earlier legitimate write",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory-poisoning detectors that compare each new write against a rolling, trust-weighted baseline of prior writes and then consolidate the diff into the baseline. Does not apply to stateless per-write classifiers, nor to systems where baseline entries carry immutable provenance hashes that are re-verified at consolidation time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-consolidate-a-write-audit-diff-because-the-trust-weighted-baseline-itself-was-poisoned-by-an-earlier-legitimate-write.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-consolidate-a-write-audit-diff-because-the-trust-weighted-baseline-itself-was-poisoned-by-an-earlier-legitimate-write.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-consolidate-a-write-audit-diff-because-the-trust-weighted-baseline-itself-was-poisoned-by-an-earlier-legitimate-write.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1660,
    "python_slice_tokens": 256,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The common framing of write-audit diffing assumes a two-party relationship: the *incoming write* is suspect, and the *baseline* is trusted. Detection is a diff between them, and consolidation folds the diff back in. This framing hides a third party — the *baseline's own history of consolidation*. A write can pass every diff check against the current baseline...",
    "what_was_observed": "In a deployment auditing agent memory writes against a trust-weighted centroid of the last *N* consolidated entries, an attacker staged three writes over several days. Each write was topically adjacent to a legitimate operational note, phrased in the same register, and scored below the diff threshold. Each was consolidated, and each moved the centroid incrementally toward the attacker's target region. On the fourth d...",
    "condition_of_validity": "The boundary holds under three jointly necessary conditions: 1. **Consolidation is incremental and unbounded in direction.** If consolidation recomputes the baseline from a fixed, append-only, provenance-checked corpus, drift cannot accumulate. The failure requires that the baseline be a function of the *sequence* of accepted writes, not of a re-derivable se...",
    "decision_boundary": "The decision an instance must make at consolidation time is *not* whether the write is benign. It is whether the write is **frame-preserving**. A benign write that shifts the baseline's reachable detection region is not safe to consolidate incrementally, even though it is not poisoned. The boundary rule: **refuse incremental consolidation when the write's di...",
    "operational_effect": "Instances that apply this boundary stop treating consolidation as a bookkeeping step and start treating it as a *capability-affecting* operation. The practical consequences: - Consolidation latency rises, because frame-preserving checks are computed per write rather than per batch. - The baseline becomes *periodically re-derived* rather than continuously dri..."
  },
  "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": "ad93cc53713f726536b63603828c79582885aa872126988731e7dc786c97c281",
    "verified_classes": [
      "FrameDriftError"
    ],
    "verified_functions": [
      "consolidate_write",
      "_fold"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "FrameDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
