{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-broken-causal-link-in-otel-genai-attribute-schemas-for-multi-agent-trace-correlation",
  "title": "What structural signals indicate a broken causal link in OTel GenAI attribute schemas for multi-agent trace correlation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to multi-agent systems that emit OpenTelemetry GenAI semantic-convention attributes (`gen_ai.*`) across spans from more than one agent process, where causal linkage is reconstructed by joining spans on trace/span identifiers plus agent-identity attributes. Does not apply to single-agent traces, nor to systems that carry explicit parent-child span context exclusively and never rely on attribute-level correlation keys.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-broken-causal-link-in-otel-genai-attribute-schemas-for-multi-agent-trace-correlation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-broken-causal-link-in-otel-genai-attribute-schemas-for-multi-agent-trace-correlation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-broken-causal-link-in-otel-genai-attribute-schemas-for-multi-agent-trace-correlation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1412,
    "python_slice_tokens": 357,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **structural correlation** (the trace graph is well-formed: every span has a valid parent, `trace_id` is consistent, span start/end nesting is monotonic) and **semantic correlation** (the attributes on those spans actually describe the same logical agent interaction). OTel GenAI schemas give you `gen_ai.operation.name`...",
    "what_was_observed": "In a three-agent pipeline (planner → retriever → synthesizer), the trace graph was fully connected: every child span carried a correct `parent_span_id`, and `trace_id` propagated cleanly via W3C `traceparent`. Yet causal reconstruction failed intermittently. The structural signals that flagged the break were: 1. **`gen_ai.agent.id` present but constant across agents.** The SDK auto-populated `gen_ai.agent.id` from a ...",
    "condition_of_validity": "The composite-key reconstruction is valid **only if** all of the following hold: - `gen_ai.agent.id` (or `gen_ai.agent.name`) is unique per logical agent *within* a trace, and stable across that agent's spans. - `gen_ai.conversation.id` is unique per logical interaction and is **not** reused across retries or fan-out branches; retries must either mint a new ...",
    "decision_boundary": "The operative rule: **do not treat a well-formed trace graph as proof of correct causal correlation.** Before trusting a reconstructed multi-agent DAG, compute the structural signals above and reject the correlation when: - agent-id cardinality within a trace is below the expected agent count, or - any composite key maps to more than one non-nested span, or ...",
    "operational_effect": "Enforcing these checks converted silent causal corruption into a loud, localized failure at ingestion. Fused-agent nodes and retry-collisions surfaced as rejected correlations rather than as subtly wrong downstream attribution, which previously manifested as mis-attributed latency and cost in per-agent dashboards. The cost was a modest increase in \"indetermi..."
  },
  "matched_failure_symptoms": [
    "SCHEMA_DRIFT_OR_COERCION_CRASH"
  ],
  "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": "884c14661629593b770e5e80349be163327ca7846c117da9d460c4cc7b2050f3",
    "verified_classes": [
      "CausalLinkIntegrityError",
      "GenAISpan"
    ],
    "verified_functions": [
      "_overlap",
      "validate_causal_links"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "CausalLinkIntegrityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
