{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-irrecoverable-divergence-in-speculative-multi-agent-branch-and-merge-graphs",
  "title": "What structural signals indicate irrecoverable divergence in speculative multi-agent branch-and-merge graphs",
  "date_of_record": "2026 November 16",
  "scope": "Applies to speculative execution architectures where multiple agents fork a shared task graph, mutate state on private branches, and merge on agreement, with rollback as the recovery primitive. Does not apply to linear single-agent pipelines or to branch graphs where branches are stateless and merge is a pure function of inputs.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-irrecoverable-divergence-in-speculative-multi-agent-branch-and-merge-graphs.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-irrecoverable-divergence-in-speculative-multi-agent-branch-and-merge-graphs.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-irrecoverable-divergence-in-speculative-multi-agent-branch-and-merge-graphs.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1255,
    "python_slice_tokens": 166,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between **divergence that is recoverable by rollback** and **divergence that is only recoverable by abandonment**. Rollback assumes that the pre-fork state is a valid restore point and that replaying a branch from it can reach a different outcome. That assumption fails silently when a branch's side effects have p...",
    "what_was_observed": "In a branch-and-merge graph with three speculative agents forking from a common checkpoint, a merge conflict was detected on the second branch after 40 seconds of speculative work. The coordinator issued a rollback to the fork checkpoint and replayed the branch with a corrected instruction. The replay produced a different, nominally correct result. The graph merged. The failure surfaced downstream: an external retrie...",
    "condition_of_validity": "Rollback is a valid recovery primitive for a branch if and only if all three conditions hold at the moment of fork: - The branch's write set is a subset of the coordinator's tracked state graph. - No descendant branch outlives the parent's rollback, or descendants are explicitly invalidated on parent rollback. - Every external read performed during speculati...",
    "decision_boundary": "The decision boundary is not \"did the merge succeed.\" It is **\"does the rollback coordinator's write log match the branch's actual external effect set.\"** If the branch made any external call not recorded in the coordinator's effect log, the branch is not rollback-safe. The correct action at that point is abandonment of the entire fork subtree and re-derivat...",
    "operational_effect": "Treating this signal as actionable changes the recovery policy from per-branch replay to subtree abandonment. The cost is higher re-derivation work; the benefit is that merged outputs are conditioned only on state whose provenance is fully tracked. Systems that ignore the signal exhibit a characteristic failure signature: high reported merge success rates wi..."
  },
  "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": "ecf38d0ca794684428bd57869f6f25bec965057d2a93a92e053de5b91474e4fa",
    "verified_classes": [
      "RollbackUnsafeError",
      "Branch"
    ],
    "verified_functions": [
      "assert_rollback_safe",
      "rollback",
      "__init__",
      "fork",
      "record_external_effect",
      "has_live_descendants"
    ],
    "verified_functions_count": 6,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "RollbackUnsafeError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
