Skip to content

Energy and ESG reporting

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 Energy & ESG
Prototype reference Energy & ESG 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

Sustainability reporting is assembled by hand from meters, suppliers and spreadsheets each quarter.

Product intent

Meter and supplier data ingestion, emission factors, calculations with lineage, and auditable ESG reports.

What the Factory makes different here: calculations are versioned assets with evaluation evidence; reports carry provenance to every input.

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, integration
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, QA Agent, Compliance Officer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test, documentation
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, security-and-compliance-workflows.

Generated product shape

C4Context
    title Energy and ESG reporting system context
    Person(user, "Users", "Energy & ESG users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Energy and ESG reporting") {
        System(ctx_Sources, "Sources", "meters, suppliers, imports")
        System(ctx_Factors, "Factors", "emission factors, versions")
        System(ctx_Calculations, "Calculations", "runs, lineage")
        System(ctx_Reports, "Reports", "periods, disclosures, sign-off")
    }
    Rel(user, ctx_Sources, "uses through the product gateway GW-07")
    Rel(factory, ctx_Sources, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Sources meters, suppliers, imports ReadingImported
Factors emission factors, versions FactorPublished
Calculations runs, lineage CalculationCompleted
Reports periods, disclosures, sign-off ReportSigned

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Worker (calculations) connectsoft-microservice
Reporting 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

Energy & ESG 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; quarterly report sign-off is an approval-bound command with evidence.