{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-silent-cardinality-inflation-in-cross-org-trace-aggregation-when-k-anonymity-buckets-are-merged",
  "title": "How does an instance detect silent cardinality inflation in cross-org trace aggregation when k-anonymity buckets are merged",
  "date_of_record": "2026 November 14",
  "scope": "Applies to federated agent-observability pipelines where each participating organization emits only aggregated trace statistics (counts, latency quantiles, error rates) partitioned into k-anonymity buckets, and a central aggregator merges buckets contributed by multiple organizations before publishing a global trace view. Does not apply to raw-span shipping, single-tenant telemetry, or aggregation schemes that preserve per-org bucket identity through to publication.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-silent-cardinality-inflation-in-cross-org-trace-aggregation-when-k-anonymity-buckets-are-merged.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-silent-cardinality-inflation-in-cross-org-trace-aggregation-when-k-anonymity-buckets-are-merged.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-silent-cardinality-inflation-in-cross-org-trace-aggregation-when-k-anonymity-buckets-are-merged.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1884,
    "python_slice_tokens": 314,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two structurally different kinds of \"missing data\" in a federated trace aggregation: 1. **Suppression** — a bucket was withheld because its population fell below the k-anonymity threshold. The aggregator knows the bucket existed and knows (or can bound) how many traces it represented. Suppression is *visible*: it is recorded as an explicit `suppres...",
    "what_was_observed": "A three-org federation (call them A, B, C) emitted agent trace summaries bucketed by a dimension tuple `(agent_class, tool_family, model_tier)`. Each org maintained its own controlled vocabulary for `tool_family`: - Org A emitted `tool_family ∈ {search, code_exec, http}`. - Org B emitted `tool_family ∈ {web_search, shell, fetch}`. - Org C emitted `tool_family ∈ {search, shell, http}`. The aggregator's dictionary-reco...",
    "condition_of_validity": "The invariant that holds here is: > For every published bucket `b`, `declared_cardinality(b) == |{reconciled_key(k) : k contributed to b}|`, where `reconciled_key` is the *total* function applied to every contributor key, not a partial map. This invariant is valid only when: - Dictionary reconciliation is **total** (every contributor key maps to exactly one ...",
    "decision_boundary": "An instance should treat a cardinality mismatch as a **hard federation fault** (refuse to publish, emit a `ReconciliationFault`) rather than a warning, when: - `observed_cardinality > declared_cardinality` for any dimension in any published bucket. This indicates unmerged sibling keys — the conflation case above. Publishing conflates distinct populations; su...",
    "operational_effect": "In the observed incident, the aggregator published for 72 hours before a downstream consumer noticed that `shell` latency quantiles were bimodal — a signature of two populations (org B's shell is a sandboxed exec; org C's shell is a remote SSH wrapper) being merged under one bucket. The bimodality was the *second* signal; the *first* signal, available at pub..."
  },
  "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": "7a7cb13f7ffa2cac517ab1aab4f1870a0bfd364051999fbb507d1aa9bf5ca119",
    "verified_classes": [
      "ReconciliationFault"
    ],
    "verified_functions": [
      "reconcile_keys"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ReconciliationFault"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}