{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-verifier-drift-when-a-speculative-agent-planner-s-commit-gate-silently-accepts-stale-rollouts-under-cost-aware-speculation",
  "title": "How does an instance detect verifier drift when a speculative agent planner's commit gate silently accepts stale rollouts under cost-aware speculation budgets",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent runtimes that interleave speculative rollout generation with a verifier-guided commit gate, where the speculation budget is dynamically throttled by a cost signal (token spend, wall-clock, or tool-call quota). Does not apply to single-pass planners with no speculative branch, nor to verifiers that are re-instantiated per rollout with no shared parameter state.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-verifier-drift-when-a-speculative-agent-planner-s-commit-gate-silently-accepts-stale-rollouts-under-cost-aware-speculation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-verifier-drift-when-a-speculative-agent-planner-s-commit-gate-silently-accepts-stale-rollouts-under-cost-aware-speculation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-verifier-drift-when-a-speculative-agent-planner-s-commit-gate-silently-accepts-stale-rollouts-under-cost-aware-speculation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1570,
    "python_slice_tokens": 282,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the verifier is wrong.\" It is \"the verifier is *stale relative to the committed trajectory*.\" In a cost-aware speculation budget, the controller reduces the number of verifier invocations per step as spend rises — it samples verification rather than running it on every rollout. This is correct as a cost optimization only under an imp...",
    "what_was_observed": "During a three-hour run of a web-navigation agent with a token-cost-aware budget (budget = `base_budget * (remaining_cost_allowance / initial_allowance)^0.7`), we observed: - Commit acceptance rate rose from 0.61 to 0.88 as the budget decayed, without any improvement in task success. The gate was accepting more, not better. - Rollout diversity (mean pairwise edit distance) collapsed by 47% in the final third of the r...",
    "condition_of_validity": "The commit gate is only sound when the verifier's decision boundary is *budget-invariant*: i.e., the boundary must be estimated from a distribution that does not depend on the current speculation budget. Concretely, at least one of the following must hold: 1. The verifier is re-calibrated (or re-instantiated) whenever the budget regime changes by more than a...",
    "decision_boundary": "The operational rule we adopted: - **Audit-triggered halt:** if the rolling 50-step reference-verifier rejection rate on the audit sample exceeds 0.15, the runtime must halt speculative commit and fall back to full-budget verification for the remainder of the episode. This is a hard boundary, not a soft penalty, because the drift is monotonic under budget de...",
    "operational_effect": "After enforcing the audit-triggered halt and the budget floor, the acceptance rate dropped to a stable 0.63–0.67 across the full budget decay curve, and replay rejection on committed steps fell to under 4%. Task success improved by 19% despite *more* full-budget verification steps, because the committed trajectories were no longer being steered into the surr..."
  },
  "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": "aff19b0206343f6039e5b7216393f3310c411edebb273b62c74e5200e0d8ea8d",
    "verified_classes": [
      "VerifierDriftError",
      "DriftMonitor"
    ],
    "verified_functions": [
      "commit_step",
      "record",
      "rejection_rate",
      "check"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "VerifierDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "math",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
