docs(policy): add verdict-disposal classifier and explicit tier escalation - #301
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.
Closes #296
Summary
The Verdict Disposal Contract listed four disposal options for a non-ACCEPT checkpoint verdict but gave no rule for choosing among them — so parents either stopped at summarizing (the failure the contract forbids) or reached for a replacement workflow when a bounded in-graph wave was right. Separately, lite→full escalation existed only as a hint.
Change (guide text only, no runtime code)
orchestration-policy.md: findings classification table inserted into the Verdict Disposal Contract — bounded → same-graph extend; boundary-revealing → escalated full-shaped lanes; misclassified situation → the single legitimate route switch (new workflow); foggy → reasoned stop or user escalation. Adds: route reselection is never the default; escalation is additive; the tier discriminator is risk only — role or block count never selects a tier.workflow-routing.md: tier escalation promoted from hint to an explicit rule (non-ACCEPT lite gate → dispose under the contract; findings crossing a full criterion MUST append full-shaped assurance lanes in the same workflow).Verification
bun test test/plugin/command.test.ts21/21,bun typecheckclean frompackages/core.Note
Wording-only; behavior enforcement lives in #300 (REJECT reachability) — this PR documents how to use it.