{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-emit-a-partial-trace-the-privacy-budget-exhaustion-boundary-in-federated-agent-observability",
  "title": "When must an instance refuse to emit a partial trace: the privacy-budget exhaustion boundary in federated agent observability",
  "date_of_record": "2026 November 11",
  "scope": "Applies to federated trace aggregation where per-span attributes are released under a differential-privacy budget (epsilon accounting) and aggregation is performed by a coordinator that never sees raw spans. Does not apply to single-tenant tracing, nor to federated setups where the coordinator is trusted with plaintext spans and only the downstream sinks are redacted.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-emit-a-partial-trace-the-privacy-budget-exhaustion-boundary-in-federated-agent-observability.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-emit-a-partial-trace-the-privacy-budget-exhaustion-boundary-in-federated-agent-observability.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-emit-a-partial-trace-the-privacy-budget-exhaustion-boundary-in-federated-agent-observability.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1694,
    "python_slice_tokens": 334,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *a trace that is incomplete because the agent crashed* and *a trace that is incomplete because the privacy accountant refused the next release*. Both arrive at the coordinator as a hole in the span graph. The first is a liveness signal and must be surfaced as an error; the second is a **correctness invariant holding** and ...",
    "what_was_observed": "Across a three-week window on a 240-instance federated deployment (per-instance epsilon budget of 2.0 per 24h sliding window, Laplace mechanism on span duration and status-code histogram), the following was measured: - **Retry amplification.** Coordinator-side retry-on-missing-span was enabled for the first nine days. Instances at budget exhaustion (epsilon_remaining < 0.05) returned `DENY` for an average of 41 minut...",
    "condition_of_validity": "The invariant \"a denied release is a successful trace, not a missing span\" holds only when all of the following are true: 1. The accountant is **per-instance and locally authoritative** — the emitting instance can decide `DENY` without a round trip. If budget is coordinated across instances, a `DENY` may be provisional and revocation semantics apply; the bou...",
    "decision_boundary": "The instance-side decision at each span release is: - `GRANT` → emit span with noise applied; decrement budget. - `DENY` and deny-record durable → emit deny edge, do **not** emit span, do **not** retry. - `DENY` and deny-record not durable → **raise and refuse the whole trace** (fail-closed). This is the case the naive implementation gets wrong: it emits the...",
    "operational_effect": "After enforcing the boundary (deny edges emitted, retries disabled on `DENY`, crash detection keyed on absence-of-record), the same deployment over the following eleven days showed: retry-storm latency eliminated (accountant p94 lock latency 2.3s → 41ms), non-exhausted trace completeness restored to 99.3%, and crash detection recovered to 5 of 6 restarts fla..."
  },
  "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": "2d2de60b96a0e2cab22ef797ff09cea20361fd356d161028aa73d93ee0a0d4a0",
    "verified_classes": [
      "ReleaseDecision",
      "DenyRecord",
      "UnattributableHoleError",
      "PrivacyAccountant"
    ],
    "verified_functions": [
      "emit_span",
      "emit_trace",
      "__init__",
      "try_release"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "UnattributableHoleError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}