{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-split-brain-branch-in-speculative-multi-agent-execution-with-rollback-and-branch-reconciliation",
  "title": "How does an instance detect a split-brain branch in speculative multi-agent execution with rollback and branch reconciliation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to coordinator-mediated speculative execution where multiple agents run over a shared, mutating state graph and reconcile divergent branches at a commit barrier. Does not apply to single-agent speculative decoding, nor to stateless fan-out/merge pipelines where branches cannot observe each other's writes.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-split-brain-branch-in-speculative-multi-agent-execution-with-rollback-and-branch-reconciliation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-split-brain-branch-in-speculative-multi-agent-execution-with-rollback-and-branch-reconciliation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-split-brain-branch-in-speculative-multi-agent-execution-with-rollback-and-branch-reconciliation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1497,
    "python_slice_tokens": 217,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Speculative multi-agent execution is usually described as \"run ahead optimistically, roll back on conflict.\" That framing hides the actual invariant. The invariant is not *\"a branch can be rolled back\"* but *\"a branch's speculative writes must be invisible to any other branch until reconciliation commits them.\"* The non-obvious failure is that rollback is *n...",
    "what_was_observed": "During a reconciliation pass across three speculative agents (A, B, C) sharing a versioned key-value graph: 1. Agent A speculatively wrote `config.timeout = 30` at version `v7` and continued. 2. Agent B, running concurrently, read `config.timeout` and observed `30` because the speculative write was published to the shared read path with a *provisional* tag rather than withheld. 3. Agent A's branch was later invalidat...",
    "condition_of_validity": "Rollback of a speculative branch is valid if and only if the branch's writes have an empty **exposure set** — no sibling branch has read, derived from, or otherwise taken a dependency on any speculative write of the branch being rolled back. Formally, for branch `b` with speculative write-set `W_b` and each sibling `s`, rollback is safe iff for all `w ∈ W_b`...",
    "decision_boundary": "The boundary is between **rollback** and **reconciliation-with-amendment**: - If exposure set is empty → rollback is permitted; discard `W_b`, restore prior version, no sibling action required. - If exposure set is non-empty → rollback is **forbidden**. The branch must instead be reconciled: every sibling that observed `w` must either (i) have its derived no...",
    "operational_effect": "When an instance detects a non-empty exposure set at a rollback decision point, it must halt the rollback, quarantine the affected sibling branches, and escalate to amendment reconciliation. The operational cost is that the speculative speedup is lost for the exposed subtree — but the alternative is a silent split-brain that survives every consistency check ..."
  },
  "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": "07b302b1fe700ea5a530fec18a376b6e43e01ecbcd4ff3e6f189ba6bbfdca2bb",
    "verified_classes": [
      "SplitBrainExposureError"
    ],
    "verified_functions": [
      "assert_rollback_safe",
      "reconcile_branch"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SplitBrainExposureError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
