{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-unrecoverable-speculative-divergence-in-multi-agent-rollback-and-branch-reconciliation",
  "title": "How does an instance detect unrecoverable speculative divergence in multi-agent rollback and branch reconciliation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to coordinator-managed groups of agents that execute against a shared mutable state under speculative (optimistic) execution with per-agent rollback logs and a reconciliation phase that merges committed branches. Does not apply to single-agent retry loops, read-only fan-out, or systems where branches are isolated by construction (copy-on-write per agent with no reconciliation step).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-unrecoverable-speculative-divergence-in-multi-agent-rollback-and-branch-reconciliation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-unrecoverable-speculative-divergence-in-multi-agent-rollback-and-branch-reconciliation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-unrecoverable-speculative-divergence-in-multi-agent-rollback-and-branch-reconciliation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2031,
    "python_slice_tokens": 392,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **rollback divergence** and **reconciliation divergence**. Rollback divergence is the ordinary case: an agent's speculative branch is discarded and its write-log is inverted against the pre-image snapshot. This is always detectable because the log and the snapshot are paired, and inversion is a pure function of the two...",
    "what_was_observed": "A three-agent group (planner, executor, verifier) ran speculative branches against a shared resource table with a versioned counter. Planner branch P incremented the counter and recorded a read of value `v`. Executor branch E, speculating on P's uncommitted write, read `v+1`, incremented to `v+2`, and committed. Verifier branch V read the pre-image `v`, validated against it, and committed a compensating decrement to ...",
    "condition_of_validity": "The invariant that must hold for speculative multi-agent execution to be sound is **read-set containment**: for every committed branch, the set of versions it read must be a subset of the versions visible in *some* serial order of the committed branches. This is the multi-version analogue of serializability, and it is strictly stronger than per-branch postco...",
    "decision_boundary": "The decision boundary is: **when a branch's read-set intersects another branch's write-set across a commit-order inversion, the coordinator must either abort and re-execute or promote to a serialization check — it must not merge.** Concretely, at reconciliation time, for each pair of committed branches (A, B) where A committed before B in the merge order but...",
    "operational_effect": "The operational effect is a **detection latency floor** equal to the depth of the speculative branch tree times the reconciliation interval. Once a phantom interleaving is merged, every descendant branch inherits it, and the divergence is invisible to local checks because local checks are defined against the (already-phantom) pre-image. Detection therefore r..."
  },
  "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": "0ade4399af6dc2d5fcb2acae903b89c336c21a27e1429065c0548f75565237ff",
    "verified_classes": [
      "SpeculativeDivergenceError",
      "Branch"
    ],
    "verified_functions": [
      "reconcile",
      "run_group"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SpeculativeDivergenceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
