- product-portfolio
- ecosystem-catalog
- deep-dives
- governance
Advanced Enterprise, Platform Governance & Strategic Services - Analysis¶
Planning-layer analysis for category 30. 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: Enterprise Governance
- Group: governance
- Default wave / cycle: Phase 6 · Continuous
- 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 |
|---|---|
| Module-in-service | 35 |
| Platform Product | 8 |
| Portal/UI Module | 6 |
| Vertical Solution Pack | 1 |
Anti-fragmentation stance
Per ADR-0011, the 35 module candidates below are delivered inside the Enterprise Governance bounded-context service, not as separate microservices. Only the 8 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1451 | Enterprise Control Plane | 4 | Planned |
| CS-SVC-1457 | Platform Governance Board Portal | 4 | Planned |
| CS-SVC-1479 | Platform Maturity Assessment | 4 | Planned |
| CS-SVC-1490 | Platform Adoption Analytics | 4 | Planned |
| CS-SVC-1493 | Executive Command Center | 4 | Planned |
| CS-SVC-1497 | Platform AI Governor | 4 | Planned |
| CS-SVC-1499 | ConnectSoft Operating Model Platform | 4 | Planned |
| CS-SVC-1500 | ConnectSoft Digital Ecosystem Control Tower | 4 | Planned |
Portal / UI Modules¶
- Context Map Designer (
CS-SVC-1465) - Enterprise Risk Dashboard (
CS-SVC-1475) - Transformation Program Portal (
CS-SVC-1477) - FinOps Governance Portal (
CS-SVC-1485) - Vendor Strategy Portal (
CS-SVC-1488) - Enterprise Search Portal (
CS-SVC-1492)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Enterprise Governance 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): Enterprise Control Plane, Multi-Product Portfolio Manager, Product Strategy Workspace, Product Roadmap Service, Portfolio Prioritization Service, Investment Planning Service, Platform Governance Board Portal, Architecture Review Board Service
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?