docs: global architecture context for Dynamic Team Mode (RFC-0055) - #413
Closed
Million-mo wants to merge 7 commits into
Closed
docs: global architecture context for Dynamic Team Mode (RFC-0055)#413Million-mo wants to merge 7 commits into
Million-mo wants to merge 7 commits into
Conversation
Synchronize RFC-0055 draft so the architecture branch has the same source of truth as the implementation branch. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Add README, vision/philosophy, and system overview documents that provide the high-level narrative for AgentPool architecture. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Explicitly state the problems Dynamic Team Mode solves and the hard constraints/principles that bound the solution space. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Compare multi-agent frameworks and map existing RFCs to the architectural layers and Team Mode phase plan. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Record the decision to add Dynamic Team Mode and link RFC-0055 to local session-management debt (issue #170) and codebase entry points. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Add 07-team-mode-design-space.md with the full design-space matrix, collaboration modes, communication patterns, lifecycle, and message handling strategies. Update README navigation. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Add 08-agent-abstraction-unification.md showing that agent types are relationships and lifecycle policies, not separate classes. Update README navigation. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
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.
docs: global architecture context for Dynamic Team Mode (RFC-0055)
Purpose
This PR does not change any code. It adds global architecture documentation so that the design intent behind Dynamic Team Mode (RFC-0055) and the surrounding AgentPool architecture can be reviewed as a coherent whole, not just through scattered code PRs and discussion comments.
Related:
What is added
docs/architecture/README.mddocs/architecture/01-vision-and-philosophy.mddocs/architecture/02-system-overview.mddocs/architecture/03-problem-space.mddocs/architecture/04-constraints-and-principles.mddocs/architecture/05-framework-comparison.mddocs/architecture/06-rfc-roadmap.mddocs/architecture/06-decisions/DDR-001-why-dynamic-team-mode.mddocs/rfcs/draft/RFC-0055-dynamic-team-mode.mdfeat/dynamic-team-modedocs/team-mode/RFC-0055-design-notes.mdWhy this matters
The current RFC and implementation are spread across
feat/dynamic-team-modeand discussion comments. This branch consolidates the reasoning so that reviewers can challenge the architecture before more implementation PRs are merged.Review focus
03-problem-space.mdaccurate?04-constraints-and-principles.mdacceptable?05-framework-comparison.mdfairly represent each option?06-rfc-roadmap.mdcorrect?RFC-0055-design-notes.md?Status
Draft. Ready for architectural review and discussion.