Vision to Production — Communication¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
This page applies the Vision-to-Production workflow to Omnichannel communication hub (example page). The steps are the Factory's reference run flow; the right-hand columns say what is specific to this vertical.
| # | Step | Platform | Specific to Communication |
|---|---|---|---|
| 1 | Run submitted with the prompt and constraints | Control plane | residency tenant-region; edition Managed |
| 2 | Policy and snapshot resolved; budget reserved | Control plane, Governance | — |
| 3 | Vision Blueprint produced and validated | Agent Mesh, Template & Library | Notifications, email, SMS and chat are wired ad hoc in every product with no delivery evidence. |
| 4 | Product plan and personas | Agent Mesh | A communication hub with templates, channels through connectors, delivery receipts and preference management that other products call. |
| 5 | Service Blueprint: contexts, aggregates, events | Agent Mesh, Template & Library | Templates, Delivery, Preferences |
| 6 | Context map and domain models derived | Template & Library (BC-02) | 3 contexts |
| 7 | Security, database, integration blueprints | Agent Mesh | integration |
| 8 | UX and frontend blueprints | Agent Mesh, UX track | localization |
| 9 | Recipe proposed from the context map | Template & Library (BC-15) | Microservice ×3, API client library, Admin MFE |
| 10 | Recipe validated against manifests and the compatibility matrix | Template & Library (BC-14) | templates: connectsoft-microservice, connectsoft-api-library, connectsoft-blazor-mfe |
| 11 | Recipe approved | Control plane (approval) | Requester or Reviewer per policy |
| 12 | Generation run: scaffold in the sandbox | Agent Mesh, Tools & MCP | Integration Architect Agent, Backend Developer Agent, QA Agent, Observability Engineer Agent |
| 13 | Tests and validators | Tools & MCP, Knowledge (artifacts) | test blueprint thresholds |
| 14 | Change proposal (branch, pull request) | DevOps / GitOps (BC-23) | shared-write class |
| 15 | Review and merge in the system of record | DevOps / GitOps | human review |
| 16 | Pipeline run with typed results | DevOps / GitOps | build, tests, scan, SBOM, images |
| 17 | Release assembled with evidence | DevOps / GitOps (BC-24) | immutable release |
| 18 | Evaluation of agent-generated assets | Observability (BC-22) | regression gates (D32) |
| 19 | Promotion to staging; verification | DevOps / GitOps, Runtime Cloud | — |
| 20 | Production promotion with approval | DevOps / GitOps (production class) | separation of duties |
| 21 | Provisioning applied; descriptor published | Runtime Cloud (BC-25), the product | Pulumi stacks; GW-07 |
| 22 | Managed-operations handover acknowledged | the product owner | Managed |
| 23 | Fleet onboarding; objectives; probes | Product Fleet Operations (BC-35) | Managed; provider connectors certified; delivery objectives per channel. |
| 24 | Feedback, learning proposals, re-scaffold on template releases | Observability (BC-22), Fleet (BC-36) | continuous |