- product-portfolio
- ecosystem-catalog
- deep-dives
- vertical
Legal, Government, Public Sector & RegTech - Analysis¶
Planning-layer analysis for category 22. 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: Legal & Government
- Group: vertical
- Default wave / cycle: Phase 5 · Cycle 5: Marketplace & Ecosystem
- 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 | 39 |
| Platform Product | 3 |
| Portal/UI Module | 6 |
| Workflow Template | 2 |
Anti-fragmentation stance
Per ADR-0011, the 39 module candidates below are delivered inside the Legal & Government bounded-context service, not as separate microservices. Only the 3 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1071 | Permit Application Platform | 4 | Planned |
| CS-SVC-1077 | Municipal Service Request Platform | 4 | Planned |
| CS-SVC-1100 | GovTech Command Center | 4 | Planned |
Portal / UI Modules¶
- Citizen Portal (
CS-SVC-1070) - Tax Filing Portal (
CS-SVC-1076) - Public Consultation Portal (
CS-SVC-1081) - Case Worker Portal (
CS-SVC-1087) - Government Analytics Dashboard (
CS-SVC-1088) - Legal Intake Portal (
CS-SVC-1091)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Legal & Government 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: critical - audit + evidence by default.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): Legal Billing Service, Digital Identity for Citizens, Regulatory Audit Trail
- Future (Tier 4-5): Legal Case Management, Matter Management Service, Contract Review AI Service, Contract Lifecycle Management, Clause Library Service, Legal Document Automation, Litigation Hold Service, eDiscovery Workflow 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?