{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-reconcile-privacy-budget-exhaustion-against-trace-completeness-in-federated-agent-observability",
  "title": "How should an instance reconcile privacy budget exhaustion against trace completeness in federated agent observability",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated agent-trace aggregation where each participating organization applies a local differential-privacy (DP) mechanism (noise injection or k-anonymity suppression) before emitting span records to a shared collector, and where the collector must decide whether a distributed trace is \"complete enough\" to reason about. Does not apply to trusted-aggregator models where raw spans cross the boundary, nor to post-hoc auditing of already-published traces.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-privacy-budget-exhaustion-against-trace-completeness-in-federated-agent-observability.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-privacy-budget-exhaustion-against-trace-completeness-in-federated-agent-observability.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-privacy-budget-exhaustion-against-trace-completeness-in-federated-agent-observability.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1782,
    "python_slice_tokens": 392,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **trace completeness** (the fraction of expected spans that arrived and survived suppression) and **privacy budget exhaustion** (the accumulated epsilon spent by a participant's local mechanism over a reporting window). These two quantities are usually treated as independent knobs: you tune epsilon to control leakage, and ...",
    "what_was_observed": "During a multi-week aggregation run across four participants (two model-serving orgs, one tool-provider, one orchestrator), the collector's completeness metric for cross-org traces began a monotonic decline around day 9, reaching 0.61 by day 14. The decline was smooth and correlated across all participants, which the on-call operator initially read as a shared upstream sampling change. It was not. Two participants ha...",
    "condition_of_validity": "The reconciliation described below is valid only when: 1. Each participant can emit a *budget-state attestation* at a granularity coarser than the span (e.g., per reporting window: `{spent_epsilon, mode: noise|suppress, k}`), and that attestation is signed by the participant. 2. The collector treats completeness as a *per-stratum* quantity, where strata are ...",
    "decision_boundary": "The collector must choose between three actions when per-stratum completeness falls below a threshold while topology completeness remains high: - **Accept** only if every stratum's coverage is above `min_stratum_coverage` *and* no participant is in `suppress` mode for that stratum's window. - **Flag-and-degrade** if topology is intact but one or more strata ...",
    "operational_effect": "Enforcing the joint condition changed three things. First, the reliability model's success-rate estimate moved back into agreement with participant-internal audits (the 18-point inflation disappeared once hollow strata were excluded or widened). Second, the collector began issuing *budget-pressure* signals to participants a full window before exhaustion, let..."
  },
  "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": "52b9117034ba087bc74be01655bd48154f7cc1e2b24a1d1d428968e2ff9c9797",
    "verified_classes": [
      "TraceCompletenessError",
      "ParticipantAttestation",
      "StratumCoverage",
      "TraceReport"
    ],
    "verified_functions": [
      "reconcile",
      "coverage"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "TraceCompletenessError"
    ],
    "sample_fail_closed_invariants": [
      "topology incomplete: parent_span_id chain broken; cannot attribute loss to privacy suppression"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
