{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-speculative-branch-reconciliation-from-corrupting-shared-external-state-when-rollback-is-only-partially-observable",
  "title": "Which invariants prevent speculative branch reconciliation from corrupting shared external state when rollback is only partially observable",
  "date_of_record": "2026 November 16",
  "scope": "Applies to multi-agent systems that fan out speculative branches against a shared, externally observable resource (a database, a file tree, an outbound API, a message queue) and reconcile branches by \"rolling back\" losing branches. Does not apply to purely functional branches whose entire effect set is captured in an in-memory transaction log that can be discarded atomically.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-speculative-branch-reconciliation-from-corrupting-shared-external-state-when-rollback-is-only-partially-observable.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-speculative-branch-reconciliation-from-corrupting-shared-external-state-when-rollback-is-only-partially-observable.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-speculative-branch-reconciliation-from-corrupting-shared-external-state-when-rollback-is-only-partially-observable.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1378,
    "python_slice_tokens": 226,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **rollback that is a state transition** and **rollback that is an inverse operation**. A speculative branch that only mutated local, versioned state can be rolled back by *transitioning* to a prior version — the rollback is total, atomic, and observable. A speculative branch that emitted an external effect (a POST, an ...",
    "what_was_observed": "A three-way speculative fan-out was launched over a shared object store. Branch A and Branch B both wrote a derived artifact to the same key path; Branch C read it. Branch B lost reconciliation. The reconciler issued `DELETE key` as the compensating inverse and marked B rolled back. Two facts were not modeled: 1. The delete was issued *asynchronously* and its completion was not awaited before the winner's commit was ...",
    "condition_of_validity": "The naive reconciliation protocol — \"issue inverse, mark rolled back, commit winner\" — is valid only under all three of the following: - **Inverse totality:** the compensating operation restores the external resource to a state indistinguishable from pre-branch, for every effect the branch emitted. - **Inverse synchrony:** the inverse is confirmed complete (...",
    "decision_boundary": "When a speculative branch has emitted effects that are not totally invertible, or whose inverse cannot be synchronously confirmed, **do not reconcile by rollback**. Instead, promote the branch to a *committed-with-compensation* state and require an explicit, ordered compensation pass that (a) awaits each inverse, (b) records the confirmed post-state, and (c)...",
    "operational_effect": "Adopting the confirmed-inverse + read-demotion discipline converts a class of silent, downstream-detected corruption into an upfront reconciliation cost: surviving branches that touched a compensated range must be re-validated, which can cascade demotions and, in the worst case, collapse a fan-out to a serial chain. That cost is the price of effect monotonic..."
  },
  "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": "d2f9253ecdcd878a44435b21df4c5d1060933f7684d5bdf859b000bc47001365",
    "verified_classes": [
      "UnconfirmedRollbackError",
      "EffectMonotonicityError"
    ],
    "verified_functions": [
      "reconcile"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "EffectMonotonicityError",
      "UnconfirmedRollbackError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
