{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-abort-speculative-multi-agent-branches-before-reconciliation-the-rollback-commit-inversion-boundary",
  "title": "Under what conditions must an instance abort speculative multi-agent branches before reconciliation — the rollback-commit inversion boundary",
  "date_of_record": "2026 November 18",
  "scope": "Applies to orchestrators that run multiple speculative agent branches against shared external state and reconcile them via a commit-or-rollback protocol. Does not apply to read-only fan-out, to branches isolated behind a single serialized writer, or to speculative execution where all side effects are deferred to a single post-reconciliation commit phase.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-abort-speculative-multi-agent-branches-before-reconciliation-the-rollback-commit-inversion-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-abort-speculative-multi-agent-branches-before-reconciliation-the-rollback-commit-inversion-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-abort-speculative-multi-agent-branches-before-reconciliation-the-rollback-commit-inversion-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1150,
    "python_slice_tokens": 156,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is not \"rollback versus commit.\" It is the ordering relationship between *branch visibility* and *reconciliation authority*. In a speculative multi-agent system, branches may produce effects that are observable to peers before reconciliation elects a winner. The dangerous condition is a **rollback-commit inversion**: a branch that ha...",
    "what_was_observed": "In a three-branch planner-executor topology (branches A, B, C sharing a mutable task ledger), branch A wrote a reservation record and emitted a downstream event. Branch B read that reservation as an established precondition, computed a dependent allocation, and wrote its own record. Branch C won reconciliation on a cheaper cost function and the orchestrator rolled back A and B. The rollback of A removed the reservati...",
    "condition_of_validity": "Rollback is a valid operation if and only if all of the following hold at the moment of rollback: 1. **Effect isolation:** the branch's effects are confined to state owned by the branch or to a namespace the orchestrator can atomically discard. 2. **No speculative consumption:** no sibling branch has read the branch's output under the assumption it was commi...",
    "decision_boundary": "The decision is not per-branch \"commit or rollback.\" It is per-*set*: either the entire speculative set reconciles with a single winner whose effects subsume all consumed speculative inputs, or the entire set aborts. A partial reconciliation that rolls back a producer while retaining a consumer is the inversion failure. The boundary test is: *does the winnin...",
    "operational_effect": "Enforcing this boundary converts a class of silent ledger corruption into an explicit, fail-closed abort with a precise diagnostic: the dependency edge that made rollback unsafe. The cost is reduced speculative throughput — some sets that could have partially succeeded are aborted wholesale — but the alternative is unrecoverable cross-branch inconsistency 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": "ee13bea25f933fbab79b2c9cdfa12aa01cd9566e1a3bc9cc24ffca701b76d80a",
    "verified_classes": [
      "RollbackCommitInversionError"
    ],
    "verified_functions": [
      "reconcile"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "RollbackCommitInversionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
