Repository navigation
Add explicit graph reservations, attempt accounting and safe bounded retry - #3
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-dispatch capacity under its existing graph lock, retain permanent consumption after dispatch, and explicitly release only proven never-dispatched reservations. An operator-selected same-node retry creates a fresh predeclared child run only after a sealed Dispatch refusal before node admission, preserving exact inputs and all earlier attempt history.
The opt-in journal-derived ledger preserves consumed effects, blocks stale/downstream-bound retries, accounts for branches and subgraphs without double counting, and participates in retained-host reconciliation and exact graph finalization. New input alpha4 and program-terminal alpha2 commitments are additive; historical bytes remain unchanged. General retries, pricing, dynamic topology and remote/distributed recovery remain outside scope.
Validation: full canonical release gate passed at 119de2e (106 suite groups, 101 native shard assertions, 55 new checks, four new vectors, 3/3 release workloads). Four-language conformance passed. Evidence includes both corrected canonical failures, the host restart interruption, exact pins and hashes in docs/evidence/graph-attempt-accounting/validation.json. Final changes after that source commit are documentation/evidence only.