Repository navigation
Bind sourced resource accounting and Eval budgets to graph authority - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dispatch can now reserve program and first-class Eval capacity together under its existing graph lock, consume Eval dispatches durably, and resolve exact evaluator results without refunding consumed work. Explicit Eval-only retry uses a new identity and the same bound program result after conclusive infrastructure failure. Branches and subgraphs use the existing DAG and separate resource dimensions.
Runtime measurements and SDK context ledgers retain exact source artifacts. Observed, provider-reported, estimated and unknown values remain distinct; incomplete totals are null. An optional source-availability policy fails closed on missing provider usage. Numeric token, runtime and monetary ceilings remain deferred because these post-hoc sources do not bound future consumption.
The canonical gate also exposed missing sibling Eval/Workcell CI fixtures. Both workflows now provision pinned dependencies through guarded aliases, and isolated recovery copies retain the complete source inventory. The host verifier manifest bound grows from 16 to 32 files; historical hashes and participant bytes remain unchanged.
Validation on
2577c60ff7ef79992f34b4627799f488cf5edcd6:37874350de7d36eaf5c34a8b7fe2767841c3c3ae: https://github.com/kujolang/dispatch/actions/runs/36896068452.docs/evidence/resource-accounting/. Source/evidence hashes verified. Changes after the tested application source contain documentation/evidence and the artifact-policy correction below; production resource code is unchanged.Post-push artifact CI rejected the intentionally retained logs under the generic log ignore. The bounded exception now passes the complete history guard and three focused guard checks; ordinary logs and missing ignore coverage still reject. The original hosted failure and correction evidence are retained. Kujo's companion PR #20 integrates the existing release-owned installation and compiler fixes.
See
docs/contracts/resources/anddocs/audits/resource-accounting.mdfor ownership, recovery, source-scope and installed-host boundaries. No new scheduler, participant wire contract, pricing engine or remote authority is introduced.The hosted recovery proof exposed a same-second refresh fixture that incorrectly expected distinct evidence bytes. The fixture now requests a distinct validity window, retaining production rejection of identical rebindings. All 29 retained-recovery proofs pass locally and in the complete hosted gates.