Repository navigation
Proposal: add a DebatePipeline (independent answers -> cross-examination -> judge synthesis) #3832
lss680455-create
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
I propose adding a
DebatePipelineto the newpipelinemodule: several peers answer the same question independently, then see each other's answers in one or more cross-examination rounds, then a single judge writes the final answer and records the disagreement that survives. It is the orchestration shape behind design reviews, review panels and contested analytical questions — and it is not expressible with the two existing pipelines (TeamPipelinekeeps members isolated from each other;GoalPipelineis one executor plus one pass/fail verifier).This is a proposal for #2479 ("if you have proposals for new pipeline types or designs, feel free to ... submit a proposal"). The full design — class and constructor,
reply_streampseudo-code, HITL / cancellation semantics, scope, and a 14-test matrix — is in issue #3828.Why a pipeline rather than an example
Concurrency, HITL routing by
reply_id, cancellation, round budget and context reset are exactly what the pipeline module exists to encapsulate. A single example would have to reimplement all of it, badly, and every user would repeat that work.Design in one screen
DebatePipeline(debaters: list[TeamMember], judge: Agent, rounds: int = 1, reset_debaters: bool = True)TeamMember,PipelineProtocol, and the HITL / cancellation machinery proven inTeamPipeline.Open questions
pipeline/the right home, or is this better as an example?TeamMember, or introduce a dedicatedDebatertype?rounds: 1 (one challenge round) or 2 (more dialectic, double the calls)?I will not open a PR until the direction is agreed.
All reactions