{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-clean-trace-context-silently-sever-the-audit-chain-during-agent-incident-replay",
  "title": "Why does an instance of \"clean\" trace context silently sever the audit chain during agent incident replay?",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-hop agent systems where safety evaluations, taint-propagation telemetry, and incident replay all depend on a shared trace/span correlation identifier that is propagated through tool calls, sub-agent invocations, and model-to-model handoffs. Does not apply to single-process agents with no external tool boundary, nor to systems where each hop mints a fresh root trace and correlation is reconstructed offline by content hashing.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-clean-trace-context-silently-sever-the-audit-chain-during-agent-incident-replay.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-clean-trace-context-silently-sever-the-audit-chain-during-agent-incident-replay.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-clean-trace-context-silently-sever-the-audit-chain-during-agent-incident-replay.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1840,
    "python_slice_tokens": 433,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct meanings of \"trace continuity\" that operational dashboards routinely conflate: 1. **Transport continuity** — the `trace_id`/`span_id` pair survives serialization across every process boundary, so the collector can stitch a single flame graph. 2. **Semantic continuity** — the *provenance* of the data flowing through the agent (untrusted...",
    "what_was_observed": "During replay of an incident in which an agent executed a destructive tool call on content that originated from an untrusted retrieved document, the following held simultaneously: - The trace was a single connected tree. `trace_id` was identical across the orchestrator, the retrieval tool, the summarizer sub-agent, and the executor. - The taint-propagation telemetry recorded the document span as `taint:untrusted` wit...",
    "condition_of_validity": "The failure is reachable only when all of the following hold: - The agent topology includes at least one **context-constructing boundary** (sub-agent spawn, tool sandbox, model handoff, or async task) that emits a new span context instead of extending the caller's. - The taint label is carried in **baggage** (or an equivalent side-channel) rather than encode...",
    "decision_boundary": "The operational rule is a single, sharp line: > **A span that shares a `trace_id` but does not carry an explicit, inherited taint label MUST NOT be treated as clean. It must be treated as `unknown`, and `unknown` must be non-executable for any action classified as irreversible.** This inverts the common default. The tempting default — \"no taint label means c...",
    "operational_effect": "When this boundary is respected, three things change: - **Safety evals become taint-aware, not trace-aware.** The eval asserts a propagation invariant (`taint label present on every span between origin and sink`) rather than a connectivity invariant. This catches the re-rooting seam that connectivity checks miss. - **Incident replay becomes causally faithful..."
  },
  "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": "66c23a30eb73a2bf7dde7a4a1a3d4457e7f347ca9aeac14f59c5c59bd79b1fdd",
    "verified_classes": [
      "TaintContinuityError",
      "Span"
    ],
    "verified_functions": [
      "assert_taint_continuity",
      "gate_action"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "TaintContinuityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
