{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-reconcile-divergent-branch-state-after-speculative-multi-agent-rollback-without-corrupting-the-causal-commit-log",
  "title": "How should an instance reconcile divergent branch state after speculative multi-agent rollback without corrupting the causal commit log",
  "date_of_record": "2026 November 15",
  "scope": "Applies to orchestrators that fan out speculative agent branches against a shared, versioned state substrate and reconcile them via causal commit ordering. Does not apply to stateless fan-out (map/reduce without shared mutation) or to systems where rollback is implemented as full-state snapshot restore rather than inverse-operation replay.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-divergent-branch-state-after-speculative-multi-agent-rollback-without-corrupting-the-causal-commit-log.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-divergent-branch-state-after-speculative-multi-agent-rollback-without-corrupting-the-causal-commit-log.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-divergent-branch-state-after-speculative-multi-agent-rollback-without-corrupting-the-causal-commit-log.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1834,
    "python_slice_tokens": 317,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *rollback of effect* and *rollback of intent*. Speculative execution produces two kinds of residue: the mutations a branch applied to shared state (effect), and the causal edges it registered in the commit log describing what it believed it depended on (intent). Most rollback implementations are correct on effect and silen...",
    "what_was_observed": "In a three-agent speculative fan-out (planner, executor, verifier) over a shared key-value substrate with per-key version vectors, the following sequence occurred during a routine rollback drill: 1. Branch B1 speculatively wrote `k=42` at version `(B1, 1)` and committed intent edge `B1 → base@v7`. 2. Branch B2 speculatively read `k`, observed `42`, and recorded a read-dependency edge `B2 → B1` plus an intent edge `B2...",
    "condition_of_validity": "The distinction above is only meaningful under the following conditions, all of which must hold: - Rollback is implemented as inverse-operation replay, so the substrate's current state does not carry a tombstone identifying *which* branch produced the reverted value. (Snapshot-restore rollback preserves lineage by construction and does not exhibit this failu...",
    "decision_boundary": "The decision is: when a speculative branch's read-validate detects that a value it depended on has changed, do you (a) re-run the sub-step against current state, or (b) abort the branch entirely and re-dispatch it from base? Choose (b) — full abort and re-dispatch — if and only if the changed value's producing commit is *unreachable* in the reconciled histor...",
    "operational_effect": "Applying the reachability test converts a silent lineage corruption into an explicit, bounded abort. In the drill above, the corrected validator aborted B2 at step 4 and re-dispatched it from base, producing a clean log with parent `base@v7` and no dangling edge. The cost was one re-dispatch of B2's sub-step; the cost of *not* doing it was a corrupted histor..."
  },
  "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": "75ee797d0a8be5801c37cc2c40a21f6bf0478252efe4d8f83c259d650859b77c",
    "verified_classes": [
      "DanglingCausalEdgeError"
    ],
    "verified_functions": [
      "validate_branch_commit",
      "reconcile"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "DanglingCausalEdgeError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
