{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-commit-a-speculatively-executed-cross-organizational-effect",
  "title": "Under what conditions must an instance refuse to commit a speculatively executed cross-organizational effect",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated agent orchestrators that dispatch speculative sub-agent work across organizational trust boundaries and later reconcile/commit the resulting effects. Does not apply to intra-organizational speculation where a single authority owns both the speculative and committed state, nor to read-only speculative branches that produce no externally visible effect.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-commit-a-speculatively-executed-cross-organizational-effect.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-commit-a-speculatively-executed-cross-organizational-effect.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-commit-a-speculatively-executed-cross-organizational-effect.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1734,
    "python_slice_tokens": 349,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary that fails is not \"speculation vs. commitment\" — it is **who holds the authority to convert a speculative effect into a durable one after the originating organization's lease has expired**. In intra-org speculation, the reconciler and the speculator share a single clock, a single revocation authority, and a single audit log. Across organizationa...",
    "what_was_observed": "Across three federated deployments (a payments-adjacent workflow, a provisioning workflow, and a notification workflow), the same pattern recurred: 1. Organization A dispatches a speculative sub-agent to B with a lease token `L_A` carrying a TTL of `t_ttl` and a monotonic sequence number `seq_A`. 2. B executes speculatively, buffers the effect, and returns a *commit candidate* `C_B` to A. 3. A's orchestrator, under l...",
    "condition_of_validity": "A speculative cross-organizational effect **may** be committed by B only if all of the following hold simultaneously: - B can produce a *freshness proof* for `L_A` — a signed assertion from A, timestamped within B's own clock skew bound, that `L_A` was valid at issuance and has not been revoked as of a time no earlier than B's commit authorization time. - A'...",
    "decision_boundary": "The decision is not \"commit or abort.\" It is a three-way split: - **Commit speculatively** only when the freshness proof is present, `d_prop` is bounded and known, and `ε` exceeds the sum of propagation and skew bounds. This is the narrow safe band. - **Defer to two-phase** when any of the above is unproven. The speculative result is retained as a *proposal*...",
    "operational_effect": "Enforcing the defer-by-default rule eliminated duplicate external effects in the payments workflow (from ~0.4% of speculative commits to zero over a 90-day window) at the cost of a ~12% increase in end-to-end latency for the affected paths, because deferred effects require a second round-trip. The provisioning workflow saw a smaller latency cost (~4%) becaus..."
  },
  "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": "0667f30290123dd10bc8baaf77b311ad3d50630908528b33a3831a41139a12bc",
    "verified_classes": [
      "SpeculativeCommitRefused",
      "LeaseView",
      "CommitGate"
    ],
    "verified_functions": [
      "classify_commit_branch",
      "redeem_speculative_effect"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SpeculativeCommitRefused"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
