Expand description
JSON schemas for the three structured exchanges.
These are what make convergence machine checkable instead of regex matching
prose for “LGTM”. Three properties are load bearing for strict structured
output and are asserted in the tests: every property appears in required,
every object sets additionalProperties: false, and an optional field is
spelled as one that may be null rather than one that may be absent.
The description on each field is also the cheapest place to ask for
brevity, since it travels with the request rather than sitting a thousand
tokens back in the prompt.
Enums§
- Criteria
Voice - Who is answering for the acceptance criteria: the author, whose word is a claim, or a reviewer, whose word is what ticks a box.
Functions§
- adjudication
- One reviewer judging the other reviewer’s findings.
- all
- answer
- One agent drafting answers to what an issue asks of the viewer.
- answer_
check - The second agent ruling on the drafted answers.
- brainstorm_
converge - The last round: defend or withdraw what was challenged, and rank the rest.
- brainstorm_
cross - A cross round: one agent ruling on ideas the other proposed.
- brainstorm_
ideas - checkin
- One agent judging the comments other people left on a pull request.
- checkin_
check - The second agent ruling on the first one’s calls.
- checkin_
fix - What the fix pass reports back about each change it was asked to make.
- code_
issue - A single actionable issue, drafted against the repository.
- implementation
- What the implementor reports back, and the pull request body it becomes.
- own_fix
- A reviewer’s report on fixing its own findings.
- recheck
- Both agents, after a reviewed pull request moved: a ruling per earlier
finding, matched back by the number the prompt gave it, and ordinary
findings for anything new in the delta. The finding item is
review()’s, so there is one definition of a finding. - response
- review
- screen
- One agent ruling on recorded follow-ups, before any becomes an issue.
- split_
check - The second agent ruling on the first one’s decomposition.
- split_
proposal - One agent decomposing one issue or one pull request.
- split_
screen - One agent ruling on a whole queue at once: is this worth splitting.
- triage
- with_
criteria schemawith a status asked for on each numbered acceptance criterion.