Skip to content

Configuration and feature management

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

Business problem

Configuration and flags are scattered across repositories and vaults; changes have no approval or audit.

Product intent

Configuration namespaces, feature flags, environments, digest-bound approvals and audit — the canonical Config Platform as a generated product.

What the Factory makes different here: the most mature prototype: separation of duties and approvals that go stale when the digest changes.

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
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent frontend, ux, localization
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Enterprise Architect Agent, Security Architect Agent, Backend Developer Agent, Frontend Developer 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: platform-evolution-workflows.

Generated product shape

C4Context
    title Configuration and feature management system context
    Person(user, "Users", "Config Platform users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Configuration and feature management") {
        System(ctx_Namespaces, "Namespaces", "namespaces, keys, versions")
        System(ctx_Flags, "Flags", "flags, rules, rollouts")
        System(ctx_Approvals, "Approvals", "proposals, digests, decisions")
        System(ctx_Audit, "Audit", "evidence, exports")
    }
    Rel(user, ctx_Namespaces, "uses through the product gateway GW-07")
    Rel(factory, ctx_Namespaces, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Namespaces namespaces, keys, versions ConfigPublished
Flags flags, rules, rollouts FlagChanged
Approvals proposals, digests, decisions ProposalApproved
Audit evidence, exports EvidenceRecorded

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Admin shell connectsoft-blazor-saas-shell
Client library connectsoft-api-library
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

Config Platform prototype (five personas 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; the Factory itself consumes the canonical Config Platform (ext-config-platform).