{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-speculative-multi-agent-branch-commit-a-partial-side-effect-when-the-reconciler-aborts-it",
  "title": "Why does an instance of a speculative multi-agent branch commit a partial side effect when the reconciler aborts it?",
  "date_of_record": "2026 November 17",
  "scope": "Applies to speculative multi-agent execution systems where agents run against a shared mutable world state (external APIs, message queues, filesystems, databases) under an optimistic fork/rollback model, and where a reconciler later selects one branch to commit and aborts the rest. Does not apply to purely computational branches with no external side effects, nor to systems that enforce a hard transactional barrier (two-phase commit) around every branch.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-speculative-multi-agent-branch-commit-a-partial-side-effect-when-the-reconciler-aborts-it.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-speculative-multi-agent-branch-commit-a-partial-side-effect-when-the-reconciler-aborts-it.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-speculative-multi-agent-branch-commit-a-partial-side-effect-when-the-reconciler-aborts-it.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1506,
    "python_slice_tokens": 220,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"rollback\" that speculative execution conflates at its peril: 1. **State rollback** — restoring the in-memory or copy-on-write snapshot the branch was forked from. This is cheap, deterministic, and always succeeds because the system owns the state. 2. **Effect rollback** — undoing side effects the branch already emitted into...",
    "what_was_observed": "A three-agent speculative fan-out (planner, executor, verifier) forked a branch to provision a customer resource. The executor branch issued an outbound `POST /provision` to an external control plane and received `202 Accepted`. The verifier branch, running concurrently against a stale snapshot, concluded the resource already existed and marked the branch redundant. The reconciler selected a sibling branch and aborte...",
    "condition_of_validity": "This boundary is live whenever all of the following hold: - Branches can emit **non-idempotent or irreversible** external effects before the reconciler decides. - The abort path destroys branch-local state **before or independently of** the compensation path reading it. - Compensation is **keyed on branch-local identifiers** rather than an effect ledger that...",
    "decision_boundary": "The operational rule is: **never let a branch emit an external effect that the orchestrator cannot independently account for.** Concretely, the decision boundary sits at the moment a branch is about to call out. At that point the orchestrator must have already durably recorded an *effect intent* — `(branch_id, effect_id, target, idempotency_key, reversible: ...",
    "operational_effect": "Systems that treat abort as atomic and synchronous exhibit **silent effect leakage** proportional to the number of aborted branches that crossed the effect boundary before abort. The leak is invisible to the orchestrator's own metrics (all branches report terminal states, all queues drain) and only surfaces in external reconciliation. The fix is structural: ..."
  },
  "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": "dfe50fbdde04d3f184896f2163769b39c9a5efa51f71a1d1af756e64ef8d365d",
    "verified_classes": [
      "IrreversibleAbortError",
      "EffectIntent",
      "EffectLedger"
    ],
    "verified_functions": [
      "abort_branch",
      "record",
      "for_branch"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "IrreversibleAbortError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
