Repository navigation
A decision as the specification says it: who is asked, what a model is shown, what is recorded - #23
Merged
Merged
Conversation
…s shown, what is recorded
The reference workflow runtime read neither `if-unsure-below:` nor
`if-it-disagrees: go-on`, recorded a decision under names the specification
does not have, and handed back a workflow's last stage where it reached no
`answer`. Found by writing a shared case for a classifier; settled with Bud
Agent Flow, which had built both lines.
- Rungs: a label stands; a `go-on` rung is a second opinion on it. Under
`if-unsure-below:`, or with no score, a classifier passes on to the next
rung, never to the next model of its own list.
- A `decide` records `.label`, `.decided-by`, `.answered-by`; every stage has
`.outcome`; a `repeat` has `.rounds` and `.ended`. A person's answer may say
who answered.
- A workflow hands back what an `answer` stage bound, and `{}` otherwise.
- A classifier is not given the stage's `says:`; what a model is shown of what
an agent was given is all of it and nothing else (`worded`).
- `loader/a-rung-with-two-kinds-of-reader` (a warning).
- Twelve shared cases on `tests/conformance/trees/triaged-defects`.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
What this is
PACT's reference workflow runtime ignored two lines the specification promises on a decision (
if-unsure-below:andif-it-disagrees: go-on), recorded a decision under names the specification does not have (by,because), and handed back a workflow's last stage where it reached noanswerstage. Found by writing a shared case for a classifier. Bud Agent Flow had built both lines; its answers settled the unwritten parts. No field of the schema changes; help text does.What a runtime must match
go-onis a second opinion, asked even while a label stands: agree and it stands; disagree or pass on, and nothing stands.scoreunderif-unsure-below:, or no score, passes on to the next rung. Exactly at the figure decides. Never to the next model of the agent's ownmodel:list..label,.decided-by(rules/agent/person),.answered-by; every stage.outcome; arepeat.roundsand.ended.answerstage bound, else{}.says:.tests/conformance/trees/triaged-defects.What
pact checknow saysloader/a-rung-with-two-kinds-of-reader(warning): one agent on a rung lists a decision model and a language model.loader/a-deciding-agent-given-nothingno longer countssays:for a classifier.Tested
scripts/test-all.shlocally: exit 0.mkdocs build --strict: exit 0.gpt-4o-mini: 10 of 10 (the live suite now sends every field an agent was given).🤖 Generated with Claude Code