{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-treat-a-reconstructed-causal-trace-as-authoritative-rather-than-advisory",
  "title": "When must an instance treat a reconstructed causal trace as authoritative rather than advisory",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent observability pipelines that reconstruct causal chains by stitching spans across federated collectors where at least one span originates from a non-deterministic replay (sampled, re-executed, or shadow-traffic) source. Does not apply to single-collector traces with monotonic logical clocks, nor to traces where every span carries a verified parent-child link from the originating runtime.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-treat-a-reconstructed-causal-trace-as-authoritative-rather-than-advisory.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-treat-a-reconstructed-causal-trace-as-authoritative-rather-than-advisory.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-treat-a-reconstructed-causal-trace-as-authoritative-rather-than-advisory.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1551,
    "python_slice_tokens": 307,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A reconstructed trace is *authoritative* when every edge in the causal chain is backed by a span-local causal token (a propagated trace context, a W3C `traceparent`, or an application-embedded parent span ID) that was written by the process that actually executed the work. It is *advisory* when any edge was inferred by the reconstruction layer — via timestam...",
    "what_was_observed": "In a federated deployment spanning three collector regions, agent replays were executed against recorded decision logs to validate policy changes. The replayer emitted spans tagged `replay=true` but reused the *original* trace ID so that operators could correlate live and replay behavior. The reconstruction layer, which joined spans across regions by trace ID and ordered by `start_time`, merged live and replay spans ...",
    "condition_of_validity": "A reconstructed edge `A → B` may be treated as authoritative if and only if all of the following hold: 1. `B` carries a causal token whose parent field names `A`'s span ID, written at execution time by `B`'s process. 2. Neither `A` nor `B` is tagged as a replay, shadow, or sampled-synthetic span, OR the reconstruction explicitly partitions replay spans into ...",
    "decision_boundary": "The boundary is not \"authoritative vs. advisory trace\" — it is **per-edge**, and it must be computed at reconstruction time and carried forward, not re-derived by consumers. A reconstruction layer that emits a single `confidence` float has already lost the information needed to make the call. The correct emission is a per-edge `authority: {authoritative | ad...",
    "operational_effect": "After the incident, the pipeline was changed to partition replay spans into a parallel graph keyed by `(original_trace_id, replay_id)` and to refuse cross-graph edge inference. The remediation agent was modified to require `authoritative` on all edges before suppressing any check; advisory edges downgrade the action to \"flag for human review.\" This eliminate..."
  },
  "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": "8fa7e9dc1960efd6614874fdd20a72d9a25664f4a7182e36d94cb8b952f816d6",
    "verified_classes": [
      "AuthorityError",
      "EdgeAuthority",
      "AdvisoryReason",
      "CausalEdge",
      "Span"
    ],
    "verified_functions": [
      "classify_edge",
      "require_authoritative_causality",
      "suppress_policy_check"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "AuthorityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
