{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-cross-org-speculative-scheduler-violate-its-latency-budget-at-the-federation-boundary-even-when-every-local-budget-is-satisf",
  "title": "Why does an instance of a cross-org speculative scheduler violate its latency budget at the federation boundary even when every local budget is satisfied?",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federated speculative multi-agent schedulers where two or more organizations each enforce a private per-hop latency budget and jointly commit to an end-to-end (E2E) budget at the federation edge. Does not apply to single-tenant schedulers, nor to federations that use a single shared clock/authority for budget accounting.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-cross-org-speculative-scheduler-violate-its-latency-budget-at-the-federation-boundary-even-when-every-local-budget-is-satisf.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-cross-org-speculative-scheduler-violate-its-latency-budget-at-the-federation-boundary-even-when-every-local-budget-is-satisf.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-cross-org-speculative-scheduler-violate-its-latency-budget-at-the-federation-boundary-even-when-every-local-budget-is-satisf.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1533,
    "python_slice_tokens": 444,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not a slow hop and not a misconfigured budget. It is the distinction between **local budget satisfaction** (each org's hop finishes within its own declared budget) and **federated budget satisfaction** (the composed path, including speculation, finishes within the E2E commitment). These diverge because speculative execution converts a serial l...",
    "what_was_observed": "In a three-org federation (A→B→C) with per-hop budgets 120/90/70 ms and an E2E commitment of 240 ms, p99 E2E latency was 291 ms while p99 per-hop latency for all three orgs stayed under their declared budgets (118/87/69 ms). The scheduler's local dashboards were green. Root cause, isolated by replaying traces with speculation disabled: with speculation on, B launched a dependent agent branch on A's speculative token ...",
    "condition_of_validity": "Per-hop budget accounting is a valid proxy for E2E latency **only when** one of the following holds: 1. Speculation is disabled at every federation hop, or 2. Speculative branches are *idempotent and resumable* across invalidation (the discarded work is not lost but checkpointed and reused), or 3. The E2E slack provisioned at the federation edge is ≥ the p99...",
    "decision_boundary": "The boundary between \"safe to federate with per-hop budgets\" and \"must provision federated slack\" is: - If `speculation_failure_rate × mean_discarded_age` is below `E2E_slack / expected_hops`, per-hop accounting is adequate. - If the *p99* of `discarded_age` at any hop exceeds `E2E_slack / (hops − 1)`, per-hop accounting is structurally unsound regardless of...",
    "operational_effect": "The observable signature is a scheduler that reports all-green locally while E2E p99 drifts upward during burst windows, with overruns clustering at the same wall-clock intervals across orgs (the invalidation wave). Remediation is one of: (a) disable speculation at the hop with the highest discarded-age p99, (b) introduce checkpointed resumption so discarded..."
  },
  "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": "ce77b9a8fbf79249c5ed37fa098597ced4aa1464e47f38362a4f9d3e01e9f478",
    "verified_classes": [
      "FederatedBudgetViolation",
      "HopBudget"
    ],
    "verified_functions": [
      "check_federation_invariant",
      "schedule_federated"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "FederatedBudgetViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "statistics"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
