Skip to content

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

Business problem

Matters, documents and deadlines are managed in email; privilege and retention are not enforced.

Product intent

Matters, parties, documents with privilege classification, deadlines and billing.

What the Factory makes different here: privilege as a classification with redaction rules; legal holds from the retention pattern.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager 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 Product Manager Agent, Security Architect Agent, Backend Developer Agent, QA Agent, Compliance Officer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent documentation, 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 Legal matter management system context
    Person(user, "Users", "Legal users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Legal matter management") {
        System(ctx_Matters, "Matters", "matters, parties, deadlines")
        System(ctx_Documents, "Documents", "documents, privilege, versions")
        System(ctx_Billing, "Billing", "time, invoices")
    }
    Rel(user, ctx_Matters, "uses through the product gateway GW-07")
    Rel(factory, ctx_Matters, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Matters matters, parties, deadlines DeadlineApproaching
Documents documents, privilege, versions DocumentFiled
Billing time, invoices InvoiceIssued

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
Shell connectsoft-blazor-saas-shell
Identity connectsoft-identity
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

Legal 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

ManagedPlus; legal holds suspend retention expiry.