Skip to content

Data platform and analytics

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

Analysts wait weeks for pipelines; data lineage and access are undocumented.

Product intent

Ingestion, cataloging, governed access and dashboards with lineage from source to report.

What the Factory makes different here: lineage and ACLs modelled like the Factory's knowledge platform (sources, ACL, provenance).

Vision-to-Production path for this vertical

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

Generated product shape

C4Context
    title Data platform and analytics system context
    Person(user, "Users", "Data users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Data platform and analytics") {
        System(ctx_Ingestion, "Ingestion", "sources, pipelines, schedules")
        System(ctx_Catalog, "Catalog", "datasets, schemas, lineage")
        System(ctx_Access, "Access", "grants, classifications, audits")
        System(ctx_Reporting, "Reporting", "reports, dashboards")
    }
    Rel(user, ctx_Ingestion, "uses through the product gateway GW-07")
    Rel(factory, ctx_Ingestion, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Ingestion sources, pipelines, schedules DatasetIngested
Catalog datasets, schemas, lineage DatasetPublished
Access grants, classifications, audits AccessGranted
Reporting reports, dashboards ReportRefreshed

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Worker (pipelines) connectsoft-microservice
Analyst shell connectsoft-blazor-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

Data 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; classification-driven retention (D31) applied to datasets.