{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-commit-a-speculative-agent-branch-after-a-rollback-has-already-touched-shared-state",
  "title": "When must an instance refuse to commit a speculative agent branch after a rollback has already touched shared state",
  "date_of_record": "2026 November 18",
  "scope": "Applies to orchestrators that fork parallel agent branches speculatively, execute them against shared mutable state (memory stores, tool side-effects, external APIs), and reconcile by committing one branch while rolling back the rest. Does not apply to purely functional sandboxes where branches have no observable side-effects, nor to single-branch sequential execution where rollback is trivially a no-op.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-commit-a-speculative-agent-branch-after-a-rollback-has-already-touched-shared-state.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-commit-a-speculative-agent-branch-after-a-rollback-has-already-touched-shared-state.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-commit-a-speculative-agent-branch-after-a-rollback-has-already-touched-shared-state.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1606,
    "python_slice_tokens": 268,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"rollback\" that orchestrators routinely conflate: 1. **Logical rollback** — the branch is marked abandoned; its outputs are discarded; the reconciler will not commit its results. This is a bookkeeping operation and is always safe, always available, and always reversible. 2. **Physical rollback** — the branch's writes to shar...",
    "what_was_observed": "A planner forked three branches (A, B, C) against a shared key-value memory store. Each branch speculatively executed tool calls and wrote intermediate facts to the store under branch-scoped keys, but also read global keys written by a prior committed turn. - Branch A wrote a derived fact `region=us-east-1` into a shared key and then failed a downstream tool call. - The reconciler initiated **physical** rollback of A...",
    "condition_of_validity": "The commit-without-revalidation shortcut is valid **only** when all of the following hold: - No physical rollback has occurred on any branch whose speculative window overlaps the committing branch's read window (i.e., rollback and read are causally ordered such that the commit branch never observed rolled-back state). - Every speculative write is journaled w...",
    "decision_boundary": "The decision procedure for the reconciler on each candidate commit: - If the branch read only branch-scoped keys and issued no external reads of shared state → **commit directly**; rollback of siblings is irrelevant. - If the branch read shared state and no physical rollback touched that state since the read → **commit directly**. - If the branch read shared...",
    "operational_effect": "Enforcing revalidation on the dirty read window converts a class of silent, delayed, cross-turn corruption into an immediate, localizable reconciliation error. The cost is latency: branches that race with rollbacks must be re-executed, and the reconciler must maintain a rollback barrier. In practice this added one re-execution per several hundred forks in th..."
  },
  "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": "ddbd386d68a8f278a4e7acdc77e2e34c982704445949ea558997ee9a95ee5809",
    "verified_classes": [
      "DirtyReadCommitError",
      "BranchState"
    ],
    "verified_functions": [
      "reconcile_commit",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "DirtyReadCommitError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
