{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-level-causal-span-link-fail-silently-when-a-subagent-re-emits-an-inherited-trace-context-after-a-fan-out-barrier",
  "title": "Why does an instance-level causal span link fail silently when a subagent re-emits an inherited trace context after a fan-out barrier",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent systems that propagate W3C Trace Context (or an equivalent traceparent-like tuple) across subagent boundaries and reconstruct causal parent-child links from span emission order. Does not apply to systems that assign a fresh trace ID at every agent boundary, nor to systems that link spans exclusively via explicit parent-span-id fields captured at span creation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-level-causal-span-link-fail-silently-when-a-subagent-re-emits-an-inherited-trace-context-after-a-fan-out-barrier.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-level-causal-span-link-fail-silently-when-a-subagent-re-emits-an-inherited-trace-context-after-a-fan-out-barrier.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-level-causal-span-link-fail-silently-when-a-subagent-re-emits-an-inherited-trace-context-after-a-fan-out-barrier.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1466,
    "python_slice_tokens": 307,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a difference between a **trace context that is inherited** and a **span that is causally owned**. When a parent agent spawns N subagents, each subagent inherits the parent's `trace_id` and the parent's current `span_id` as its `parent_span_id`. The inherited span is a *reference*, not an *ownership claim*. The failure mode described here occurs when...",
    "what_was_observed": "In a three-tier agent topology (orchestrator → planner subagents → tool-executor subagents), a fan-out of six planners was joined at a barrier span `B`. Each planner emitted a `plan.complete` span with `parent_span_id = O` (the orchestrator's span), which is correct: the planners were spawned by `O`, and `B` is a synthetic join marker, not a causal parent. After `B` resolved, the orchestrator emitted a `synthesize` s...",
    "condition_of_validity": "The invariant — *a span's `parent_span_id` must denote the span whose completion is a precondition for this span's emission* — holds only if context propagation is **barrier-aware**. It fails when any of the following hold: 1. The subagent captures its inherited context at spawn time and reuses that captured tuple after a join, rather than re-reading the orc...",
    "decision_boundary": "The decision is whether to trust `parent_span_id` as a causal assertion or to treat it as a *hint* that must be cross-validated against span timestamps and barrier membership. The boundary: - **Trust `parent_span_id`** only when every span's `start_time` is ≥ its parent's `start_time` and ≤ its parent's `end_time`, *and* the parent is not a synthetic join ma...",
    "operational_effect": "Left uncorrected, this boundary failure corrupts three downstream consumers: (a) **causal attribution** — the synthesizer's output is credited to the orchestrator's direct reasoning rather than to the planners' aggregate, inflating orchestrator contribution metrics; (b) **critical-path analysis** — latency accounting double-counts the fan-out because the syn..."
  },
  "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": "41420df30fa8bc071d401b316f096f97004231bdfe3729ef1de30056e605cef0",
    "verified_classes": [
      "CausalLinkViolation",
      "Span"
    ],
    "verified_functions": [
      "validate_causal_link",
      "repair_post_barrier_parent"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "CausalLinkViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
