Enterprise governance and risk¶
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 | Enterprise Governance |
| Prototype reference | Enterprise Governance 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¶
Policies, controls and audits are tracked in documents nobody can query.
Product intent¶
Policy registry, control mapping, audit campaigns and findings with evidence, modelled like the Factory's own governance.
What the Factory makes different here: reuses the Factory governance patterns (policy bundles, evidence chains) as product features.
Vision-to-Production path for this vertical¶
| Step | Factory platform | Agents | Blueprints |
|---|---|---|---|
| Vision and product plan | Agent Mesh, Control plane | Enterprise Architect Agent, Security Architect Agent | vision |
| Architecture and domain | Template & Library (BC-02) | Enterprise Architect Agent | service, module, security, database |
| Experience | Template & Library, Factory Studio UX track | UX Designer Agent, Frontend Developer Agent | — |
| Recipe and generation | Template & Library (BC-15), Agent Mesh, Tools & MCP | Enterprise Architect Agent, Security Architect Agent, Backend Developer Agent, Compliance Officer Agent, QA Agent | module plan from the context map |
| Quality | Observability (BC-22), DevOps / GitOps | QA Agent | 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: security-and-compliance-workflows.
Generated product shape¶
C4Context
title Enterprise governance and risk system context
Person(user, "Users", "Enterprise Governance users and operators")
System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
System_Boundary(product, "Enterprise governance and risk") {
System(ctx_Policies, "Policies", "policies, versions, scopes")
System(ctx_Controls, "Controls", "controls, mappings, owners")
System(ctx_Audits, "Audits", "campaigns, findings, evidence")
}
Rel(user, ctx_Policies, "uses through the product gateway GW-07")
Rel(factory, ctx_Policies, "descriptor, health, rollouts, incidents, off-boarding")
Bounded contexts¶
| Context | Responsibility | Published events |
|---|---|---|
| Policies | policies, versions, scopes | PolicyPublished |
| Controls | controls, mappings, owners | ControlAssigned |
| Audits | campaigns, findings, evidence | FindingRaised |
Modules and templates¶
| Module | Template | Notes |
|---|---|---|
| Microservice ×3 | connectsoft-microservice |
|
| Shell | connectsoft-blazor-saas-shell |
|
| 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¶
Enterprise Governance 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; audit evidence retained 7 years.