{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-abandon-speculative-multi-agent-execution-and-collapse-to-a-single-authoritative-branch",
  "title": "In what scenarios must an instance abandon speculative multi-agent execution and collapse to a single authoritative branch",
  "date_of_record": "2026 November 16",
  "scope": "Applies to orchestrators that fork a task into N parallel agent branches speculatively, commit the first branch to pass a validator, and roll back losers via compensating actions. Does not apply to read-only fan-out, map-reduce over immutable inputs, or branches whose side effects are fully isolated in per-branch sandboxes with atomic swap-on-commit.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-abandon-speculative-multi-agent-execution-and-collapse-to-a-single-authoritative-branch.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-abandon-speculative-multi-agent-execution-and-collapse-to-a-single-authoritative-branch.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-abandon-speculative-multi-agent-execution-and-collapse-to-a-single-authoritative-branch.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1529,
    "python_slice_tokens": 291,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"divergence\" in speculative multi-agent execution, and conflating them is the failure mode. **Observational divergence** is when branches produce different outputs from the same input — this is the *expected* condition that speculation exists to exploit; the fastest correct branch wins and the rest are pruned. **Causal diver...",
    "what_was_observed": "A three-branch speculative executor was tasked with provisioning a resource: branch A reserved an ID from a shared monotonic allocator, branch B wrote a partial record to a downstream queue, branch C (the eventual winner) passed the validator and committed. Rollback of A and B was issued as compensating actions. The compensating \"release\" for A returned the ID to a free-list, but the allocator had already handed that...",
    "condition_of_validity": "Branch-and-prune rollback is valid only when all of the following hold simultaneously: 1. **Effect fencing.** Every branch's outbound effects are held in a buffer keyed to the branch, releasable only on commit. If any effect escapes the buffer before commit, the condition fails. 2. **Compensation idempotence and non-interference.** Each compensating action m...",
    "decision_boundary": "The decision is not \"did branches diverge\" but \"has any branch crossed an irreversible-effect boundary before commit.\" The orchestrator must classify each branch's effect stream at fork time into *buffered* (safe to prune) and *emitted* (irreversible). The moment any branch emits an irreversible effect while siblings are still live, the speculative window is...",
    "operational_effect": "When this boundary is respected, speculative execution degrades gracefully: wide fan-out where effects are bufferable, narrow or single-branch where they are not, with a clean handoff at the emission point. The cost is reduced parallelism on tasks with early side effects — which is the correct trade, because the alternative is silent corruption of external s..."
  },
  "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": "9801045e49e5ab17e677ea7bdabcfc05b0872bfca4c008d4585135e31ea3098e",
    "verified_classes": [
      "SpeculativeBoundaryError",
      "EffectClass",
      "Branch"
    ],
    "verified_functions": [
      "prune_losers",
      "run_speculative",
      "has_emitted"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SpeculativeBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
