Veni AI Sustainability Cockpit combines ERP connector sync, canonical fact modeling, retrieval, verification, and controlled publish into one open-source sustainability reporting workflow.
The product is designed for teams that need more than a static ESG dashboard. It turns connector-fed data into audit-ready report packages with evidence, calculation traces, and tracked artifacts.
The architecture keeps SAP, Logo Tiger, and Netsis integrations separate at the connector layer, then normalizes every record into a canonical fact shape before narrative generation or packaging begins.
Fail-closed trust rules ensure the system does not publish unsupported claims: no evidence, no claim; no calculator artifact, no numeric claim; no verifier pass, no publish.
ERP-to-package disclosure workflow
Built for teams that need SAP, Logo Tiger, and Netsis signals to become publish-ready TSRS and CSRD report packages.
The system synchronizes ERP inputs, normalizes every accepted record into canonical facts, verifies claims against evidence and calculation traces, and only publishes when package gates stay green.
Connector Matrix
Each connector preserves its own delta semantics and ingest contract, but every accepted record is normalized into a traceable disclosure object before it can influence narratives or package status.
OData pull with ERP-grade freshness tracking for energy, emissions, and governance signals.
Best suited for climate, electricity, and governance metrics that need source-system lineage and repeatable sync jobs.
Read-only SQL View sync for workforce, safety, and committee cadence metrics.
Captures operational and people metrics without writing back into the ERP, while keeping replay and support diagnostics visible.
REST pull for supplier, materiality, and stakeholder engagement disclosures.
Supports supply chain and disclosure-planning flows where cursor-based deltas and API-level diagnostics matter.
Canonical + Trust
Records do not flow straight into narrative text. They become canonical facts that carry business meaning, ownership, unit discipline, and evidence-ready lineage before any disclosure logic runs.
{
"metric_code": "E_SCOPE2_TCO2E",
"period_key": "2025",
"unit": "tCO2e",
"value_numeric": 12450,
"source_system": "sap_odata",
"source_record_id": "sap-scope2-2025",
"owner": "[email protected]",
"confidence_score": 0.98,
"trace_ref": "sap://scope2/2025"
}What every fact carries
Period-aware facts
Every metric is anchored to a reporting period so year-on-year analysis and disclosure scope stay explicit.
Unit normalization
Units are standardized before package composition so emissions, ratios, counts, and rates stay comparable.
Ownership and confidence
Each fact records who owns the metric and how confident the system is in the normalized output.
Traceable disclosures
Source ids and trace refs keep each claim connected to the originating ERP object or evidence lane.
Fail-closed publish rules
No evidence, no claim
Narrative statements must resolve to evidence-backed citations before they become package-eligible.
No calculator artifact, no numeric claim
Numeric language is blocked unless the system can point to a deterministic calculation artifact.
No verifier pass, no publish
Critical FAIL states and missing approval-chain conditions stop controlled publish until the blockers are cleared.
Package Flow
The system treats publish as a tracked package pipeline rather than a blind PDF shortcut. That means stage history, artifact completeness, and verifier readiness remain visible all the way to release.
Pull certified ERP connector data into project-specific run context.
Transform source rows into canonical facts with units, owners, and trace refs.
Map facts and evidence into disclosure-ready section scaffolds.
Generate narrative drafts only after structure and context are in place.
Run claim-level citation and numeric checks before package completion can continue.
Prepare decorative visuals, charts, and tracked visual manifest slots.
Assemble the PDF and supporting JSON exports from verified package state.
Register output metadata, stage history, and artifact inventory.
Release only when verification, approval, and artifact gates all stay green.
Disclosure frameworks in scope
Governance and risk-management disclosure flows align the board, policy, and oversight story.
Climate and energy sections focus on emissions, electricity mix, and operational reduction narratives.
Workforce and supply-chain narratives connect social, materiality, and supplier coverage metrics.
Why the flow matters
Publish model
Tracked package jobs, not instant blind downloads
Trust posture
Evidence-backed, calculation-aware, approval-gated
Operator view
Status, lanes, artifacts, and verifier pressure stay visible
Product Surfaces
The open-source product already exposes the reporting workflow as a working control room: from new run setup to retrieval diagnostics, evidence ingest, and package release.
01
Connector freshness, KPI strip, verifier pressure, package lanes, artifact health, and recent run movement in a dense executive cockpit.
The open-source product already exposes the reporting workflow as a working control room: from new run setup to retrieval diagnostics, evidence ingest, and package release.
02
A report factory launchpad for company profile, brand kit, framework scope, governance owners, and connector selection.
03
Upload source files, run OCR or queued extraction, inspect index health, and keep raw payload visibility for evidence operations.
04
Tune hybrid retrieval queries, scoring thresholds, period hints, and disclosure tags before claims move toward publish.
05
Execute runs, clear triage pressure, refresh package status, and download tracked artifacts from one release surface.
Report Output + OSS
This is not just a dashboard concept. The repository already contains generated report previews, package artifacts, and a multi-service implementation spanning web, API, worker, data, and AI services.
Generated cover preview
Generated governance page
License
MIT
Monorepo
Web + API + Worker + Connector Agent
Local runtime
Docker Compose ready
Tracked package artifacts
report_pdf
Final PDF package with report narrative, bookmarks, and polished document output.
visual_manifest
A tracked inventory of decorative visuals, source type, and AI-generation flags.
citation_index
Claim-to-evidence mapping export for traceability and audit review.
calculation_appendix
Numeric calculation references used to justify quantitative statements.
coverage_matrix
Section coverage summary across required metrics and appendix references.
assumption_register
Structured list of assumptions captured during package generation.
Implementation stack
The public repository exposes connector onboarding, canonical fact sync, report generation, retrieval, verification, packaging, and downloadable artifacts. It is positioned as a real implementation baseline rather than a marketing mockup.