{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-a-speculative-token-before-commit-in-federated-agent-execution",
  "title": "Under what conditions must an instance reject a speculative token before commit in federated agent execution",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated speculative agent execution where a lead orchestrator (the *speculator*) emits speculative tokens or actions that downstream instances (the *validators*) may execute before cross-org commit is confirmed. Does not apply to single-org speculative decoding, nor to federated systems where no validator executes speculative work before a commit barrier.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-speculative-token-before-commit-in-federated-agent-execution.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-speculative-token-before-commit-in-federated-agent-execution.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-speculative-token-before-commit-in-federated-agent-execution.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1436,
    "python_slice_tokens": 240,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **speculative acceptance** (a validator provisionally executing a token/action to save latency) and **speculative commit** (a validator making the effect of that token externally observable or durable). Most federated designs conflate these because in single-org systems the two are separated only by a memory fence. In cros...",
    "what_was_observed": "In a three-org federation (speculator Org A, validators Org B and Org C), tokens streamed from A were provisionally executed by B and C against a shared action log. Under nominal conditions, B and C produced identical speculative states. Under a partition between A and C (A still reachable from B), A continued emitting tokens whose validity depended on a cross-org quorum that included C. B accepted and *committed* th...",
    "condition_of_validity": "A speculative token may be accepted *and committed* by a validator only if, at accept time, the validator can establish one of: 1. The token's commit does not depend on any fact held exclusively by another org (it is locally decidable), or 2. The validator holds a verifiable, non-revocable commit certificate from the required quorum *before* making effects d...",
    "decision_boundary": "The boundary is not \"is the token valid?\" but \"**is the token's commit decidable from facts this validator can verify without trusting the speculator's future behavior?**\" Concretely, reject-before-commit when: - The commit barrier requires a quorum the validator cannot observe (partition, or the speculator suppresses negative acks). - The token's validity w...",
    "operational_effect": "Validators that enforce reject-before-commit on missing certificates lose speculative throughput during partitions (they fall back to non-speculative execution until the barrier confirms) but never commit effects the federation later disowns. Validators that skip the check gain latency under nominal conditions and accumulate *orphaned commits* — durable effe..."
  },
  "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": "c2b541552b18b820ba5ab930b8a67d49f15db589e0430fa457ccee0a58a7c0ea",
    "verified_classes": [
      "SpeculativeCommitError"
    ],
    "verified_functions": [
      "may_commit_speculative_token"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "SpeculativeCommitError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
