Repository navigation
Support verified GoalPipeline subworkflows as TeamPipeline members #3984
Leeminjing
started this conversation in
Ideas
Replies: 1 comment
|
I would like to move this proposal into a dedicated Issue for design discussion and contribution tracking. Would a maintainer be willing to convert it, or confirm that I may open a linked feature Issue? I will wait for core-team feedback before starting implementation. |
0 replies
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.
I would like to propose allowing named
GoalPipelineinstances to participate as members ofTeamPipeline, so a leader can delegate work that includes execution, independent verification, rework, and human approval as one assignment.For example, the leader delegates “implement the payment API.” The executor produces a first version, the verifier requests changes, and the executor revises it. The verifier then requests human approval before accepting the second version.
The entire sequence would remain one team assignment. Internal replies and reports would represent progress; the leader would receive one overall result containing the accepted report when the subworkflow reaches a conclusion.
One possible API would be:
Proposed behavior
(leader_reply_id, tool_call_id).accepted,impossible, andexhaustedwould be explicit outcomes. Execution failures and cancellation would follow failure and cleanup paths.team.get_assignment(leader_reply_id, tool_call_id)API would return a deep-copy snapshot of the phase, pending requests, verification rounds, overall result, and commitment state.Valid verification decisions and report/verdict format retries would have separate budgets. Human approval and waiting would neither consume nor reset those budgets.
Scope and implementation direction
Supported member types would remain limited to
Agent | GoalPipeline. Ordinary Agent members and standalone GoalPipeline usage should retain their existing behavior. This proposal would add no runtime dependencies and require no prerequisite code PRs.My proposed implementation would share one private Goal execution driver between standalone and team-managed use, reuse Team’s existing scheduling, and introduce private adapters for the two supported member types. Goal state would remain owned by GoalPipeline, assignment state by TeamPipeline, and shared result models would contain data only.
One boundary requiring design feedback is how Team observes actual parent-result commitment. The tentative approach is a private, scoped Agent receipt recorded synchronously after result storage and the
FINISHEDtransition, without adding a public hook. This would distinguish actual commitment from an emitted result-end event, including when context compression later removes the original content.The once-only settlement guarantee would apply to assignments managed within the current process. Arbitrary pipeline members, recursive teams, durable recovery, external side-effect rollback, and a public lifecycle protocol are outside the proposal.
The planned contribution is one main-repository feature PR covering 14 files: six core files, six test files, and two example files. A separate docs companion PR would update the English and Chinese team/goal pages.
This proposal was prepared against
6047bc0. No implementation or tests have been run for this feature; implementation would follow discussion and start from the then-current main.Feedback requested
All reactions