Skip to content

Insurance policy administration

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 Policy
Prototype reference Policy 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

Quotes, policies and claims are on a mainframe; product changes take quarters.

Product intent

Products and rating, quotes, policies, endorsements and claims with rating rules as versioned assets.

What the Factory makes different here: rating rules as evaluated assets with regression gates before publication.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Vision Architect Agent, Enterprise Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, 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 Vision Architect Agent, Enterprise Architect Agent, Backend Developer Agent, Database Engineer 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: enterprise-and-system-architecture-workflows.

Generated product shape

C4Context
    title Insurance policy administration system context
    Person(user, "Users", "Policy users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Insurance policy administration") {
        System(ctx_Products, "Products", "products, rating rules")
        System(ctx_Quotes, "Quotes", "quotes, binds")
        System(ctx_Policies, "Policies", "policies, endorsements, renewals")
        System(ctx_Claims, "Claims", "claims, reserves, payments")
    }
    Rel(user, ctx_Products, "uses through the product gateway GW-07")
    Rel(factory, ctx_Products, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Products products, rating rules RatingRulePublished
Quotes quotes, binds QuoteBound
Policies policies, endorsements, renewals PolicyIssued
Claims claims, reserves, payments ClaimSettled

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Rating library connectsoft-library
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

Policy 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.