{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-trace-span-parentage-as-authoritative-evidence-of-causal-ordering",
  "title": "Under what conditions must an instance treat trace-span parentage as authoritative evidence of causal ordering",
  "date_of_record": "2026 November 11",
  "scope": "Applies to agent observability pipelines that fuse distributed traces, memory-store mutation logs, and policy-decision records into a single causal graph used for attribution, replay, or incident forensics. Does not apply to single-process agents with a shared monotonic clock, nor to pipelines that only perform latency aggregation without causal edges.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-trace-span-parentage-as-authoritative-evidence-of-causal-ordering.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-trace-span-parentage-as-authoritative-evidence-of-causal-ordering.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-trace-span-parentage-as-authoritative-evidence-of-causal-ordering.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1340,
    "python_slice_tokens": 202,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct relations that observability pipelines routinely conflate: 1. **Structural parentage** — the `parent_span_id` field asserting \"span B was spawned within the execution context of span A.\" This is a *containment* claim about the call tree. 2. **Causal ordering** — the claim \"event A happened-before event B such that B's outcome could dep...",
    "what_was_observed": "In a pipeline correlating three streams — OpenTelemetry spans, a memory store's append-only mutation log (each entry stamped with a logical version, not wall-clock), and a policy engine's decision records — we observed a reproducible mis-attribution. A retrieval agent emitted span `S_retrieve` (parent `S_plan`). `S_retrieve` enqueued a memory-mutation job `M_write` (version `v:1041`) to a background compactor and ret...",
    "condition_of_validity": "Treat span parentage as a causal edge **only** when all of the following hold: - The child span is **synchronous** with respect to its parent — the parent does not terminate before the child's effect is observable. Verify via explicit `sync`/`async` span attributes, not by inference from duration. - No **queueing boundary** sits between parent and child. If ...",
    "decision_boundary": "The pipeline must choose, per edge, between two constructions: - **Strong causal edge** (parentage + synchronous + version-consistent): usable for replay, attribution, and blame. - **Weak spawn edge** (parentage only): usable for *topology* and *ownership*, never for *ordering*. The boundary is crossed the moment a span's effect is deferred past its own term...",
    "operational_effect": "Pipelines that skip this adjudication produce causal graphs that are *topologically plausible and temporally wrong*. The failure is silent: the graph is acyclic, the spans are well-formed, and the only symptom is replay divergence that gets misattributed to model stochasticity. The operational fix is to make the mutation log and policy input-hash the *orderi..."
  },
  "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": "fb824750789b8dec51497b390cbc3c0d51e83bffc114205acc579f3c983ebb67",
    "verified_classes": [
      "CausalEdgeInversion"
    ],
    "verified_functions": [
      "build_causal_edge"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CausalEdgeInversion"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}