{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-a-speculative-branch-be-treated-as-uncommitted-the-read-after-rollback-visibility-boundary-in-parallel-multi-agent-execution",
  "title": "Where must an instance of a speculative branch be treated as uncommitted: the read-after-rollback visibility boundary in parallel multi-agent execution",
  "date_of_record": "2026 November 15",
  "scope": "Applies to systems where multiple agent branches execute speculatively against a shared mutable substrate (memory store, tool side effects, or message bus) and a commit arbiter selects one or more branches to finalize. Does not apply to isolated sandboxes with copy-on-write semantics that guarantee no cross-branch observation, nor to single-branch speculative execution.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-speculative-branch-be-treated-as-uncommitted-the-read-after-rollback-visibility-boundary-in-parallel-multi-agent-execution.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-speculative-branch-be-treated-as-uncommitted-the-read-after-rollback-visibility-boundary-in-parallel-multi-agent-execution.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-speculative-branch-be-treated-as-uncommitted-the-read-after-rollback-visibility-boundary-in-parallel-multi-agent-execution.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1410,
    "python_slice_tokens": 189,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *branch-local state* and *substrate-visible state*. A branch is \"uncommitted\" in the logical sense from the moment it begins; it is \"uncommitted\" in the operational sense only while no other live branch can observe its writes. The boundary failure occurs when a speculative branch's writes become visible to a sibling br...",
    "what_was_observed": "In a three-branch speculative planner (branches A, B, C; arbiter selects by score), the following sequence reproduced on a shared Redis-backed scratch namespace with per-branch key prefixes but a shared \"derived facts\" cache keyed by content hash: 1. Branch A writes fact `f1` and derives `f2 = g(f1)`, inserting `f2` into the shared content-addressed cache. 2. Branch B, executing concurrently, queries the cache for `f...",
    "condition_of_validity": "The invariant \"a committed branch's derivation is closed under committed facts\" holds only if at least one of the following is enforced: - **Observation isolation:** sibling branches cannot read each other's writes at any layer (store, cache, memo, bus), enforced by capability scoping rather than naming convention. - **Provenance-tracked reads:** every read ...",
    "decision_boundary": "Treat a branch as **uncommitted-and-quarantined** (its writes must not enter any shared read path) when *any* of the following is true: - The branch's commit status is not yet `COMMITTED` and the substrate permits cross-branch reads. - The read path is a cache or memo whose invalidation is not tied to branch lifecycle. - The arbiter's decision can be revised...",
    "operational_effect": "Enforcing the boundary costs one of: a provenance column on every read (cheap, requires arbiter cooperation), or a staging layer between branch writes and shared reads (moderate, adds a materialization step at commit), or full read isolation (expensive, kills cross-branch information sharing that speculative execution exists to exploit). The engineering trad..."
  },
  "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": "0431d1e2202980059816fa778544c514e38916502a83ce28c6f7b556520fc58f",
    "verified_classes": [
      "GhostDerivationError",
      "ReadRecord",
      "Branch"
    ],
    "verified_functions": [
      "commit_branch"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "GhostDerivationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
