docs(eve): additive delivery plan for subagents as tasks - #1492
Closed
ruiconti wants to merge 1 commit into
Closed
Conversation
Add an implementation-sequencing plan for the subagents-as-tasks design (#1482): strictly additive stages behind experimental.tasks, with the agent-messaging stack (am/01-04) as the addressing baseline instead of a second session-addressing mechanism. Signed-off-by: Rui Conti <ruiconti@gmail.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Folded into #1482 — the plan doc is meaningless without the design doc it references, and both were unmerged single-doc branches off |
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
1 participant
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.
Summary
experimental.tasksam/01-contracts…am/04-surface) as the addressing baseline: agent handles, continuation dispatch, and theTurnCallerenvelope satisfy the design doc's A2A dependency, so tasks composes with handles instead of introducing a second session-addressing mechanismAlso records the gaps to resolve in flight:
task_sendvsAGENT_BUSY, remote children outliving the parent, blocked-vs-computing visibility before the flag ships, and the MCP failure-taxonomy decision.Companion to #1482. Part of #1084.