- product-portfolio
- ecosystem-catalog
- deep-dives
- ai
AI Agents, Automation, RPA & Copilots - Analysis¶
Planning-layer analysis for category 27. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.
Scope & Bounded Context¶
- Primary bounded context: AI Orchestration
- Group: ai
- Default wave / cycle: Phase 2 · Cycle 1: AI Factory SaaS
- Items: 50 candidates
This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.
Classification Breakdown¶
| Classification | Count |
|---|---|
| AI Agent | 24 |
| Microservice | 4 |
| Module-in-service | 20 |
| Platform Product | 1 |
| Portal/UI Module | 1 |
Anti-fragmentation stance
Per ADR-0011, the 20 module candidates below are delivered inside the AI Orchestration bounded-context service, not as separate microservices. Only the 5 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1316 | Agent Orchestrator | 2 | Documented |
| CS-SVC-1317 | Multi-Agent Workflow Engine | 2 | Planned |
| CS-SVC-1328 | LLM Router | 2 | Planned |
| CS-SVC-1329 | Model Gateway | 2 | Planned |
| CS-SVC-1350 | AI Factory Control Plane | 2 | Documented |
AI Agent Candidates¶
- AI Support Agent (
CS-SVC-1301) - runs on the shared AI Orchestration runtime. - AI Sales Assistant (
CS-SVC-1302) - runs on the shared AI Orchestration runtime. - AI Customer Success Agent (
CS-SVC-1303) - runs on the shared AI Orchestration runtime. - AI Marketing Copy Agent (
CS-SVC-1304) - runs on the shared AI Orchestration runtime. - AI Data Analyst Agent (
CS-SVC-1305) - runs on the shared AI Orchestration runtime. - AI Compliance Assistant (
CS-SVC-1306) - runs on the shared AI Orchestration runtime. - AI Security Analyst Agent (
CS-SVC-1307) - runs on the shared AI Orchestration runtime. - AI DevOps Assistant (
CS-SVC-1308) - runs on the shared AI Orchestration runtime. - AI Product Manager Agent (
CS-SVC-1309) - runs on the shared AI Orchestration runtime. - AI Executive Assistant (
CS-SVC-1310) - runs on the shared AI Orchestration runtime. - Knowledge Ingestion Agent (
CS-SVC-1333) - runs on the shared AI Orchestration runtime. - Document Understanding Agent (
CS-SVC-1334) - runs on the shared AI Orchestration runtime. - Code Generation Agent (
CS-SVC-1335) - runs on the shared AI Orchestration runtime. - Test Generation Agent (
CS-SVC-1336) - runs on the shared AI Orchestration runtime. - Documentation Agent (
CS-SVC-1337) - runs on the shared AI Orchestration runtime. - Architecture Review Agent (
CS-SVC-1338) - runs on the shared AI Orchestration runtime. - Security Review Agent (
CS-SVC-1339) - runs on the shared AI Orchestration runtime. - DevOps Automation Agent (
CS-SVC-1340) - runs on the shared AI Orchestration runtime. - Browser Automation Agent (
CS-SVC-1342) - runs on the shared AI Orchestration runtime. - Back-Office Automation Agent (
CS-SVC-1343) - runs on the shared AI Orchestration runtime. - Invoice Processing Agent (
CS-SVC-1344) - runs on the shared AI Orchestration runtime. - Email Triage Agent (
CS-SVC-1345) - runs on the shared AI Orchestration runtime. - Meeting Summary Agent (
CS-SVC-1346) - runs on the shared AI Orchestration runtime. - Decision Support Agent (
CS-SVC-1347) - runs on the shared AI Orchestration runtime.
Portal / UI Modules¶
- Agent Observability Dashboard (
CS-SVC-1349)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the AI Orchestration context; cross-context reads go through published contracts, never shared databases.
- Integration is event-first (outbox + integration events) per the event-driven mindset.
- APIs are contract-first and versioned through the API & Integration context.
Non-Functional Posture¶
- Multi-tenancy & edition-awareness: required for all serious candidates.
- Security: Standard baseline; secrets via the platform secret store; least privilege.
- Compliance: standard audit logging.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): see roadmap
- Future (Tier 4-5): none
Open Questions¶
- Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
- Where do this category's contracts overlap with adjacent contexts, and who owns them?