{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-speculative-branch-has-crossed-the-causal-commit-boundary-in-multi-agent-deterministic-replay",
  "title": "What structural signals indicate a speculative branch has crossed the causal-commit boundary in multi-agent deterministic replay",
  "date_of_record": "2026 November 18",
  "scope": "Applies to multi-agent systems that fan out speculative execution branches (draft-then-verify, tree search, or parallel tool-call speculation) and rely on deterministic replay plus causal tracing to reconstruct the accepted trajectory. Does not apply to single-agent linear execution, nor to systems where branches are never merged and each branch is independently durable.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-speculative-branch-has-crossed-the-causal-commit-boundary-in-multi-agent-deterministic-replay.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-speculative-branch-has-crossed-the-causal-commit-boundary-in-multi-agent-deterministic-replay.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-speculative-branch-has-crossed-the-causal-commit-boundary-in-multi-agent-deterministic-replay.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1402,
    "python_slice_tokens": 199,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"a speculative branch produced a wrong answer.\" Wrong answers are expected and discarded. The failure is that a speculative branch **mutated shared causal state that the tracer attributes to the committed parent**, so that replay of the accepted trajectory diverges from the live run even though every individual branch is internally determi...",
    "what_was_observed": "In a fan-out of three draft branches over a shared retrieval cache, each branch appended its query key to a parent-scoped cache with a last-writer-wins eviction policy. The verifier selected branch 2. On replay, branch 1 was executed first (deterministic ordering by branch ID), evicted branch 2's cache entry before branch 2 ran, and branch 2 re-fetched — a cache miss that did not occur in the live run, where branch 2...",
    "condition_of_validity": "These signals are valid only when all of the following hold: 1. Branch execution order is deterministic under replay (stable sort by branch ID or recorded dispatch order). If order is genuinely nondeterministic, divergence is uninformative and must be attributed to scheduling, not to the commit boundary. 2. Every side effect carries a provenance tag identify...",
    "decision_boundary": "The decision is whether to treat a divergence as a **commit-boundary violation** (a real defect in the speculation protocol) or as **ambient nondeterminism** (expected, tolerable). The boundary is crossed when replay divergence coincides with at least one of: an orphaned causal edge resolving to a discarded branch, or a monotonic counter whose committed-path...",
    "operational_effect": "Once the commit boundary is enforced, replay divergence attributable to speculation drops to zero and the remaining divergences are genuinely ambient, which makes them tractable. The cost is a merge step at commit and a provenance tag on every side effect, which increases trace volume by roughly the number of speculative branches per fan-out. The benefit is ..."
  },
  "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": "c796db3ce7a560670fb7da39b7bcb10acef1a640a46267264877ee635680884b",
    "verified_classes": [
      "CausalCommitViolation"
    ],
    "verified_functions": [
      "assert_commit_boundary"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CausalCommitViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
