Bounded-Context Map¶
This document groups the ~1,500 candidates into a manageable set of bounded contexts. It is the bridge between the flat catalog and a realistic service topology. It is anchored to the SaaS framework DDD blueprint and must stay consistent with it.
Foundational Contexts¶
These power every product and map to catalog categories 1-10, plus AI orchestration and marketplace.
| Bounded Context | Catalog categories | Responsibility |
|---|---|---|
| Tenant Management | 1 | Tenant lifecycle, provisioning, isolation, residency |
| SaaS Core Metadata | 1 | Products, editions, plans, packaging, dependency graph |
| Identity & Access | 2 | AuthN/AuthZ, sessions, tokens, RBAC/ABAC, federation |
| Config & Feature Flags | 3 | Configuration, flags, entitlements, policy/rules |
| Billing & Subscriptions | 4 | Pricing, subscriptions, invoicing, payments, metering |
| Notifications & Webhooks | 5 | Email/SMS/push/in-app, webhooks, short links |
| Audit & Compliance | 6 | Audit trail, evidence, privacy, retention, governance |
| Data & Analytics | 7 | Ingestion, quality, search, BI, lineage |
| AI Orchestration | 7, 27 | Model gateway, prompts, RAG, agents, guardrails |
| API & Integration | 8 | Gateways, connectors, contracts, eventing, sync |
| Infrastructure & SRE | 9 | Provisioning, observability, reliability, runtime |
| Developer Factory | 10 | Scaffolding, pipelines, QA, codegen, control tower |
| Marketplace & Ecosystem | 28 | App store, partners, listings, payouts |
| Enterprise Governance | 30 | Portfolio, architecture board, maturity, FinOps |
Vertical Contexts¶
Each composes foundational contexts and adds only industry-specific aggregates.
| Bounded Context | Catalog categories |
|---|---|
| CRM & Support | 11 |
| Sales & RevOps | 12 |
| Marketing & Growth | 13 |
| Commerce | 14 |
| Banking & FinTech | 15 |
| Insurance | 16 |
| Healthcare | 17 |
| Education & HR | 18 |
| Logistics | 19 |
| Manufacturing & IoT | 20 |
| Real Estate & PropTech | 21 |
| Legal & Government | 22 |
| Finance Ops | 23 |
| Media & Content | 24 |
| Hospitality & Travel | 25 |
| Energy & ESG | 26 |
Per-Context Definition Template¶
Each context (detailed in the deep-dives) is described by: responsibility, ubiquitous language, owned data/aggregates, published APIs and events, dependencies, services included/excluded, team-ownership candidate, deployment model, and risk level.
Context Relationships¶
flowchart TB
Tenant[Tenant Management]
Identity[Identity and Access]
Meta[SaaS Core Metadata]
Config[Config and Flags]
Billing[Billing and Subscriptions]
Audit[Audit and Compliance]
Notif[Notifications and Webhooks]
API[API and Integration]
Data[Data and Analytics]
AI[AI Orchestration]
Verticals[Vertical Contexts]
Tenant --> Meta
Identity --> Tenant
Config --> Meta
Billing --> Meta
Verticals --> Identity
Verticals --> Billing
Verticals --> Notif
Verticals --> Audit
Verticals --> API
AI --> Data
API --> Audit
Hold "Alt" / "Option" to enable pan & zoom