Add agent and services architecture plan with dynamic tools registry #82
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.
Problem
Outline a feasible architecture for agents that work across go-micro services, with service discovery, standardized protocols, and a monetization model.
Design
Two-Component Architecture
Agent Layer: Claude-based agent with dynamically generated tools registry. Tools are automatically built from service metadata rather than hardcoded—when a new service registers, it becomes immediately available as an agent capability.
Service Marketplace: Registry where developers publish go-micro services. Each service declares methods, schemas, and pricing. 70% revenue to developer, 30% to platform.
Protocol
Example Flow
Deliverables
Three planning documents under
docs/:Integrated into docs navigation under "Planning" category.
Open Questions
No implementation—pure design specification ready for stakeholder review.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.