{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-irreconcilable-speculative-branches-before-committing-a-multi-agent-rollback",
  "title": "How does an instance detect irreconcilable speculative branches before committing a multi-agent rollback?",
  "date_of_record": "2026 November 15",
  "scope": "Applies to systems where multiple agent instances execute speculative branches against shared external state (tool calls, file mutations, remote APIs) under a rollback-and-reconcile protocol. Does not apply to read-only speculative fan-out, nor to branches whose side effects are fully idempotent and version-fenced by the downstream tool itself.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-irreconcilable-speculative-branches-before-committing-a-multi-agent-rollback.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-irreconcilable-speculative-branches-before-committing-a-multi-agent-rollback.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-irreconcilable-speculative-branches-before-committing-a-multi-agent-rollback.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1188,
    "python_slice_tokens": 178,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"a branch failed.\" It is \"two branches succeeded against state that cannot be reconciled because each branch's tool-call validation was evaluated against a *pre-speculation* snapshot.\" A speculative branch validates its tool calls against the state it inherited at fork time. When two branches both mutate a resource and both pass valid...",
    "what_was_observed": "During a three-branch speculative execution over a shared configuration store, branches A and B each issued a `set_replica_count` tool call. A validated `3 -> 5` against snapshot `S0`. B validated `3 -> 7` against the same `S0`. Both passed. The tool had no compare-and-swap; it was a plain put. The reconciler received two post-states, `5` and `7`, both claiming parent `3`. Neither is derivably wrong, and neither is d...",
    "condition_of_validity": "The detector below is valid only when: 1. Every speculative branch records the exact snapshot token (`S0`) it validated against, and that token is attached to each tool-call validation record. 2. Resource identity is stable and comparable across branches (no aliasing of the same logical resource under two names). 3. The reconciler runs *before* any branch's ...",
    "decision_boundary": "The boundary is: **commit only if the set of (resource, snapshot_token) validation records across all surviving branches is pairwise consistent — i.e., for every resource, all branches that validated against the same snapshot token produced mutually derivable post-states, or exactly one branch touched it.** If two branches validated the same resource against...",
    "operational_effect": "Failing closed at validation time converts a two-stage-latent divergence into an immediate, localized abort with the exact resource and snapshot lineage in the error. The cost is reduced speculation yield on hot shared resources; the benefit is that rollback is always sound because no non-compensable write was ever dispatched from an irreconcilable set. Oper..."
  },
  "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": "ebac32b70ae4403b9256bc8edaa2af68087d41b60cbcb0b0ee4ee7ca101ca9bd",
    "verified_classes": [
      "IrreconcilableSpeculationError",
      "ValidationRecord"
    ],
    "verified_functions": [
      "assert_reconcilable"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "IrreconcilableSpeculationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
