{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-propagate-a-traceparent-across-an-organizational-handoff",
  "title": "Under what conditions must an instance refuse to propagate a traceparent across an organizational handoff",
  "date_of_record": "2026 November 14",
  "scope": "Applies to distributed trace correlation when a span originating in one trust domain (org A) is handed to an agent or service operating in a different trust domain (org B), where the trace context is carried via W3C `traceparent`/`tracestate` headers or equivalent. Does not apply to intra-organizational handoffs, nor to handoffs where both parties share a single signing authority for trace context.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-a-traceparent-across-an-organizational-handoff.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-a-traceparent-across-an-organizational-handoff.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-a-traceparent-across-an-organizational-handoff.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1593,
    "python_slice_tokens": 230,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious failure is not \"trace context is lost.\" Loss is loud and recoverable. The boundary failure is **trace context is silently accepted and re-emitted under a foreign trust root**, producing a trace that appears complete (single trace ID, contiguous parent chain, plausible timing) but whose causal claims are unverifiable because the `traceparent` ...",
    "what_was_observed": "In a multi-agent handoff where agent A (org A) delegated a subtask to agent B (org B) via a tool-call envelope, the envelope carried `traceparent: 00-<trace-id>-<span-id>-01` with the `sampled` flag set. Agent B correctly parented its spans to the received `span-id` and returned a completed sub-trace. Downstream, org A's collector stitched the two into one trace. Three defects surfaced: - **Span ID collision under ad...",
    "condition_of_validity": "A foreign `traceparent` may be propagated and joined into a shared trace **if and only if** at least one of the following holds: - The receiving domain has an out-of-band trust anchor tying the claimed originating authority to the `trace-id` (e.g., a signed handoff envelope, or a pre-shared trace-context signing key per W3C Trace Context Level 2 semantics). ...",
    "decision_boundary": "The decision to refuse propagation is triggered by the conjunction: Note the third clause. If the consumer only needs correlation (dashboards, latency histograms), propagation is safe and refusal would be pedantic. The refusal is mandatory only when the trace feeds a system that treats parentage as fact: audit logs, billing attribution, cross-agent causal re...",
    "operational_effect": "Refusing direct parentage and falling back to a linked, boundary-marked trace costs you a single trace tree. It buys you a causal graph whose edges are true. In practice: - **Cost:** Dashboards that assumed one trace per user request now show two (or a tree plus a link set). Tooling must understand `link` semantics. This is a real integration cost and is why..."
  },
  "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": "41fd36aacdfe0c03af865ac27566fa8596d112efc0b51b23e96366228f36154e",
    "verified_classes": [
      "TraceBoundaryViolation"
    ],
    "verified_functions": [
      "join_foreign_span",
      "enforce_tracestate_integrity"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "TraceBoundaryViolation"
    ],
    "sample_fail_closed_invariants": [
      "tracestate exceeds W3C limits on ingress"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}