Skip to content

Omnichannel communication hub

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.
Vertical Communication
Prototype reference Communication prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Notifications, email, SMS and chat are wired ad hoc in every product with no delivery evidence.

Product intent

A communication hub with templates, channels through connectors, delivery receipts and preference management that other products call.

What the Factory makes different here: every delivery is a connector delivery with receipts and replay (BC-17 pattern inside the product).

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Integration Architect Agent, Backend Developer Agent
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent localization
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Integration Architect Agent, Backend Developer Agent, QA Agent, Observability Engineer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent observability, test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: software-engineering-workflows.

Generated product shape

C4Context
    title Omnichannel communication hub system context
    Person(user, "Users", "Communication users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Omnichannel communication hub") {
        System(ctx_Templates, "Templates", "message templates, locales")
        System(ctx_Delivery, "Delivery", "channel routing, receipts, retries")
        System(ctx_Preferences, "Preferences", "opt-ins, quiet hours")
    }
    Rel(user, ctx_Templates, "uses through the product gateway GW-07")
    Rel(factory, ctx_Templates, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Templates message templates, locales TemplatePublished
Delivery channel routing, receipts, retries MessageDelivered, DeliveryFailed
Preferences opt-ins, quiet hours PreferenceChanged

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
API client library connectsoft-api-library
Admin MFE connectsoft-blazor-mfe
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Communication prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed; provider connectors certified; delivery objectives per channel.