{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-speculative-execution-from-corrupting-cross-org-reconciliation-in-federated-multi-agent-workflows",
  "title": "Which invariants prevent speculative execution from corrupting cross-org reconciliation in federated multi-agent workflows",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated workflows where two or more organizations run agents that speculatively execute steps on shared or mirrored state, then reconcile via a commit/abort protocol across trust boundaries. Does not apply to single-org speculative execution (where a shared transactional store provides serializability) or to stateless fire-and-forget agent fan-out with no reconciliation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-speculative-execution-from-corrupting-cross-org-reconciliation-in-federated-multi-agent-workflows.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-speculative-execution-from-corrupting-cross-org-reconciliation-in-federated-multi-agent-workflows.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-speculative-execution-from-corrupting-cross-org-reconciliation-in-federated-multi-agent-workflows.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1489,
    "python_slice_tokens": 155,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure that matters is not \"speculation produced a wrong answer.\" It is \"speculation produced an answer that was *correct under the speculator's local read set* but was committed against a *reconciled read set that no longer matches*.\" In a single organization this is caught by read-set validation at commit (optimistic concurrency control). Across organ...",
    "what_was_observed": "Two orgs, A (initiator) and B (counterparty), run a federated procurement workflow. A's planner agent speculatively drafts a purchase order against B's published price catalog (version `cat-441`), while B's pricing agent concurrently rotates the catalog to `cat-442` because a supplier contract lapsed. B publishes the new catalog and *retains* `cat-441` as \"valid until reconciliation epoch E_B=9182\" to allow in-flight...",
    "condition_of_validity": "The reconciliation is safe only when all four hold simultaneously: 1. **Epoch monotonicity:** each org exposes a strictly monotonic epoch counter that increments on every authoritative-state change, and the counter is the *only* authority for ordering commits — never wall clocks, never vector-clock-free timestamps. 2. **Two-valued token state, explicitly sep...",
    "decision_boundary": "Do **not** attempt cross-org speculative commit when the counterparty cannot expose an epoch counter or cannot perform the token check inside its durable commit write. In that case, degrade to *pessimistic reservation*: the speculator acquires a lease on the read tokens before executing, and the counterparty blocks supersession until the lease expires or is ...",
    "operational_effect": "Enforcing the four invariants converts a silent cross-org corruption into a loud, localized abort at the commit boundary. In the procurement case, the PO would have aborted with a supersession error at the reconciliation step, and the planner agent would have replayed against `cat-442`, producing a PO at the corrected price with a clean audit trail. The meas..."
  },
  "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": "74c27c95e54944a12aa59c4f7e9e514dc01a4e1548405de4961c7dcff3776168",
    "verified_classes": [
      "SupersededReadTokenError",
      "ReadToken"
    ],
    "verified_functions": [
      "assert_commit_legal",
      "reconcile_speculative_commit",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SupersededReadTokenError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
