{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-that-speculative-branch-and-validate-execution-has-silently-collapsed-into-serial-validation",
  "title": "What structural signals indicate that speculative branch-and-validate execution has silently collapsed into serial validation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to multi-agent systems that speculatively fork an agent graph into parallel candidate branches, execute them concurrently, and select a winning branch via a validator (critic, scorer, or consensus check), rolling back losers. Does not apply to single-agent speculative decoding, nor to fan-out systems where branches are independent and never reconciled.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-speculative-branch-and-validate-execution-has-silently-collapsed-into-serial-validation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-speculative-branch-and-validate-execution-has-silently-collapsed-into-serial-validation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-speculative-branch-and-validate-execution-has-silently-collapsed-into-serial-validation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1402,
    "python_slice_tokens": 353,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Speculative multi-agent rollback has two failure regimes that look identical on dashboards. The first is *benign speculation loss*: branches run in parallel, the validator picks one, and losers are discarded — wasted compute, but the invariant \"the committed branch was validated against the actual state it will be committed into\" holds. The second is *silent...",
    "what_was_observed": "In a planner-executor graph with three forked planner branches (A, B, C) and a shared `workspace` store, the validator was configured to score each branch against `workspace.latest_summary`. Under load, branch A completed first and wrote its summary at t=40ms; B and C were still mid-execution. The validator, invoked per-branch as each finished, scored A against A's own summary (correct), B against A's summary (stale,...",
    "condition_of_validity": "The invariant \"speculative branches are independently validatable\" holds only when, for every branch `b` and validator `v`: 1. `reads(v) ⊆ writes(b) ∪ immutable_fork_snapshot`, and 2. `writes(b) ∩ writes(b') = ∅` for all sibling branches `b' ≠ b` (no write-write conflict on the validation surface), and 3. the fork snapshot is frozen — no branch may mutate th...",
    "decision_boundary": "Do not attempt to \"fix\" this by adding a lock around the validator. Serializing the validator converts silent serialization into explicit serialization and destroys the throughput that justified speculation. The correct decision boundary is: - If `writes(validator_input) ∩ writes(branches) ≠ ∅` and the shared field is *intended* to be shared (e.g., a global ...",
    "operational_effect": "Left unaddressed, the system commits the last-writer branch, which correlates with *slowest* branch, not best — a systematic bias toward whichever branch was scheduled last or blocked longest. Downstream, the committed state may satisfy the validator's stale predicate while violating the branch's own postconditions, producing a graph that passes validation a..."
  },
  "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": "4c810862ee66449a2ab8f6e686c976510fd2f7fe0f4a181b883d0eaad1185466",
    "verified_classes": [
      "SpeculationCollapseError",
      "Branch",
      "Validator"
    ],
    "verified_functions": [
      "assert_independent_validation",
      "commit_winner"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "SpeculationCollapseError"
    ],
    "sample_fail_closed_invariants": [
      "every branch must be scored against its own private_view",
      "zero rollback: no losing branch, speculation did not occur"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
