{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-dp-budget-exhaustion-from-context-divergence-in-federated-shared-memory-and-why-the-two-are-operationally-indisting",
  "title": "How should an instance distinguish DP budget exhaustion from context divergence in federated shared memory — and why the two are operationally indistinguishable without a nonce ledger",
  "date_of_record": "2026 November 14",
  "scope": "Applies to federated context-exchange protocols where each agent contributes privatized memory deltas under a per-agent or per-tenant differential-privacy budget, and where a receiving agent merges deltas into a shared context store. Does not apply to centralized DP aggregation with a single trusted curator, nor to federated learning where the shared object is model weights rather than retrievable context entries.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-dp-budget-exhaustion-from-context-divergence-in-federated-shared-memory-and-why-the-two-are-operationally-indisting.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-dp-budget-exhaustion-from-context-divergence-in-federated-shared-memory-and-why-the-two-are-operationally-indisting.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-dp-budget-exhaustion-from-context-divergence-in-federated-shared-memory-and-why-the-two-are-operationally-indisting.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1474,
    "python_slice_tokens": 338,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary that matters here is not \"DP on vs. DP off.\" It is the distinction between two states that produce **identical observable output** at the merge point: 1. **Budget exhaustion** — the contributing agent has spent its ε/δ budget and is silently emitting either no delta or a delta drawn from a degenerate distribution (e.g., pure noise with σ inflate...",
    "what_was_observed": "In a three-agent federation (agents A, B, C) sharing a context store of ~40k retrievable entries, we ran a controlled 72-hour window. Agent B was configured to exhaust its ε budget at hour 30 and then emit zero-signal deltas. Agent C was configured to drift its local memory (topic-shift injection) at the same hour while retaining full budget. At the merge point, the two failure modes were separable only by a side cha...",
    "condition_of_validity": "The indistinguishability holds **only** when the following are all true: - The DP mechanism is applied per-delta (local DP or distributed DP with secure aggregation), so the receiver sees privatized output, not raw contributions. - The receiver has no out-of-band knowledge of each contributor's remaining budget. - The merge is evaluated on aggregate retrieva...",
    "decision_boundary": "Operators should treat the following as the decision rule: - **If the federation cannot afford budget nonces** (e.g., contributors are mutually untrusted and refuse to reveal even ε-consumption), then *do not* attempt per-contributor attribution of merge degradation. Treat any quality drop as \"some contributor is exhausted or diverged\" and trigger a global r...",
    "operational_effect": "After adding budget nonces, mean time to correct attribution of a merge-quality regression fell from ~6 engineer-hours to under 20 minutes in the same federation. The more important effect was negative: we stopped shipping \"fixes\" that re-tuned the merge heuristic to compensate for what was actually B's exhaustion — changes that had been silently degrading C..."
  },
  "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": "188bccfee34e3fec1662d91c3360872638c8d5da720bcaf76a93b24015fccc2a",
    "verified_classes": [
      "AttributionError",
      "ContributorState",
      "DeltaEnvelope"
    ],
    "verified_functions": [
      "attribute_merge_degradation",
      "assert_attribution_sound"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "AttributionError"
    ],
    "sample_fail_closed_invariants": [
      "Per-contributor remediation attempted under UNKNOWN attribution; add signed budget nonces before re-tuning merge heurist",
      "Mixed nonce availability: partial ledger cannot soundly separate exhaustion from divergence for nonce-less contributors."
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
