bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(roadmaps): clarify reuse across agent platform gaps

Browse Source
This commit is contained in:
root 2026-03-14 14:40:43 +00:00
parent f02ff801cb
commit 3cc35e2b51
1 changed files with 33 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
docs/roadmaps/not-started/platform_AGENT_PLATFORM_GAP_ROADMAP_INDEX.md
View File

@ -68,6 +68,39 @@ unless a later ADR explicitly changes them:
---
## Reuse Map
These roadmaps are **not** intended as ten pure greenfield systems. The repo already
contains partial foundations that should be extended wherever possible.
| Roadmap | Existing Components To Reuse Or Extend | New Work vs Extension |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Agent Runtime & Orchestration | `packages/queue`, `services/platform-service/src/modules/jobs`, `services/mcp-server/src/modules/a2a` | Mostly extension with one new system-of-record module |
| Org, Workspace & RBAC | `services/platform-service/src/modules/auth`, `services/platform-service/src/modules/auth/enterprise`, current membership model in auth types | New tenant model built on existing auth |
| Agent Registry & Prompt Versioning | `services/mcp-server/src/modules/tools`, A2A pipelines, existing blob/storage packages | New registry layer, but runtime integration should reuse current MCP/A2A assets |
| Knowledge & RAG Service | `services/extraction-service`, `services/platform-service/src/modules/ai-diagnostics`, `packages/extraction`, storage/blob packages | Mostly extension plus a new shared retrieval module |
| Human Review & Approval Queue | `services/platform-service/src/modules/auth/push-approvals`, `services/platform-service/src/modules/delivery`, `packages/queue` | New generalized review domain built from existing approval and delivery primitives |
| Support Case Management | `services/platform-service/src/modules/diagnostics`, `services/platform-service/src/modules/audit`, `services/mcp-server/src/modules/support/debug-pack.ts` | New case domain with heavy reuse of diagnostics context |
| Durable Event Bus & Worker Runtime | `packages/events`, `packages/queue`, existing background job patterns in `platform-service` | Direct extension, not greenfield |
| AI Governance & Evaluation | `services/extraction-service/evals`, `services/platform-service/src/modules/ai-diagnostics`, flags/experiments infrastructure | New governance surface built on existing eval/diagnostic pieces |
| AI Budget & Cost Governance | `services/platform-service/src/modules/usage`, `plans`, `subscriptions`, `licenses`, `telemetry` | Extension of existing usage/billing controls with AI-specific attribution |
| Enterprise Provisioning & SCIM | `services/platform-service/src/modules/auth/enterprise`, current auth and membership structures, queue/runtime primitives for reconciliation | Extension of enterprise auth, not a separate identity platform |
---
## What Is Truly Net-New
Only a few parts are genuinely net-new platform domains:
- canonical org/workspace/team model
- agent registry and prompt versioning as a data system
- generalized human review queue
- support case records
Everything else should start by extending current packages or modules.
---
## Existing Repo Signals
These gaps are not theoretical. The current codebase already shows the partial