{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-propagate-a-federated-trace-context-across-an-organizational-trust-boundary",
  "title": "Under what conditions must an instance refuse to propagate a federated trace context across an organizational trust boundary",
  "date_of_record": "2026 November 16",
  "scope": "Applies to distributed tracing propagation between agents operated by distinct organizations where the receiving side will re-emit spans or child trace contexts into its own trust domain. Does not apply to intra-organizational trace propagation, nor to read-only trace export to an observability backend that does not re-propagate context.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-a-federated-trace-context-across-an-organizational-trust-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-a-federated-trace-context-across-an-organizational-trust-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-a-federated-trace-context-across-an-organizational-trust-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1894,
    "python_slice_tokens": 357,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is not \"trusted vs. untrusted peer\" but **propagate vs. re-emit**. A trace context (trace ID, span ID, trace flags, baggage) entering an agent is either (a) consumed locally and dropped, or (b) re-emitted as the parent of new spans that the agent will itself propagate onward. Case (a) is a data-ingestion problem governed by data-...",
    "what_was_observed": "In a federated deployment across three organizations (A, B, C), agent B accepted inbound trace contexts from A and re-emitted them as parents of its own spans, which it propagated to C. C's policy engine used trace-level attributes (baggage carrying a `tenant_id` and a `data_classification`) to make routing decisions. Three concrete failures were observed: 1. **Baggage forgery by an honest-but-compromised upstream.**...",
    "condition_of_validity": "A federated trace context may be re-emitted across a trust boundary only when all of the following hold: - **Signed provenance.** The inbound context carries a verifiable signature over `(trace_id, span_id, parent_span_id, baggage, issuer, issued_at)` from a principal whose key the receiving agent can validate against an out-of-band trust root — not a key ca...",
    "decision_boundary": "The operational rule reduces to a single predicate evaluated at ingest: When the predicate is false, the agent must not refuse the *request* (the business transaction may still be valid) — it must refuse the *propagation*. This is the subtle part: teams conflate \"reject the trace context\" with \"reject the call.\" The correct behavior is to accept the call, de...",
    "operational_effect": "After enforcing boundary termination, three measurable effects appeared: - **Trace count increased ~40%** at the boundary (each cross-org hop now starts a new local trace), but **false causal edges dropped to zero** in the assembler. The trace graph became a forest of per-org trees linked by a shared `correlation_id` attribute, which is the honest representa..."
  },
  "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": "fb4c026d55803ab1384a4a60aab1561aaf3a6a1494bb5456896082e86bd8a5c6",
    "verified_classes": [
      "FederatedTraceBoundaryError",
      "TraceContext"
    ],
    "verified_functions": [
      "assert_reemittable",
      "handle_inbound"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "FederatedTraceBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
