Repository navigation
Conversation
|
@Retsumdk is attempting to deploy a commit to the nkkko's projects Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
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.
Adds a new pattern, Fleet Cost Simulation Before Dispatch, under Reliability & Eval.
The pattern: replay an agent fleet's budget, priority, and failure-recovery policy against deterministic scenarios (baseline / stress / starvation / deadline / token-bucket) before dispatching real work, so budget exhaustion and starvation verdicts are found in simulation instead of being paid for in production tokens, API quota, and dollars.
bun run build:dataexecuted; README TOC and site data regenerated. The incidentalgithub-stars.jsoncount drift from the rebuild is excluded to keep the diff single-purpose.validate:patternsandvalidate:patterns:contentboth pass; the only warnings are pre-existing heading-order warnings on unrelated upstream patterns.Related to the fair-share task queues pattern merged in #176 — that one covers who gets the task; this one covers whether the fleet can afford to run it.