Platform Architecture
Source-to-report evidence spine.
Four immutable layers. The boundary between them is the platform's most durable competitive moat. Reports cannot mint metrics. ERP Ratings cannot bypass Evidence. GoalNetZero cannot rewrite ratings.
Layer 1 - Evidence
Backend
Capture - Immutability - Provenance
Your facility data lands once, with provenance. No re-keying, no spreadsheet handoffs, no drift between source and disclosure.
- BACnet polling, /ingest endpoints, ERP-connector pulls, IoT MQTT topics
- Raw payload preserved + structured form in canonical hypertables
- Evidence hash on arrival; append-only audit trail
- Per-domain time series exposure across IAQ, energy, water, fuel
Layer 2 - Sector intel
ERP Ratings
Sector posture - Ratings - Risk
Sector-aware ratings in your sector's vocabulary, not a one-size-fits-all template. The healthcare CFO, the datacenter VP, the petrochemical CSO each see what matters in their world.
- Executive triplet: status, key risk, priority action
- E / S / G pillar scores plus overall band
- Risk overview, confidence, evidence maturity
- Sector-aware intelligence — healthcare, data centers, petrochemicals, financial services, and 16 other sectors
Layer 3 - Trajectory
GoalNetZero
Forward-looking - Readiness
Forward-looking trajectory and readiness intelligence. What your CFO and CSO need before SBTi submission, before carbon credits, before regulator filings.
- Climate trajectory: indicative annual reduction vs current
- Targets and progress timeline with intervention points
- Net Zero and SBTi Readiness with strict-readiness language
- Carbon Credit Readiness with eligibility screen
Layer 4 - Output
Reports
Compose - Render - Anchor
This is where ESG reporting changes posture. Today most reports are hand-cobbled. EcoVeraZ produces a tamper-proof immutable evidence chain where every value resolves to its source. Auditors don't have to trust EcoVeraZ — they verify independently with openssl in under sixty seconds.
- Composition engine selects sections by sector, framework, portfolio context
- HTML to PDF via Puppeteer; SHA-256 content hash over report.json plus sidecars
- RFC 3161 trusted-timestamp anchor (FreeTSA in development; commercial TSA in production)
- Six-sidecar audit trail per render: methodology pack, machine-readable payload, proof anchor, evidence manifest, artifact manifest, composition decisions
The boundary promise
Every value resolves to a dataset_id in the Backend.
Re-render from report_id on any environment - SHA-256 content fingerprint matches exactly. The RFC 3161 serial verifies independently via openssl ts -verify. Formal certification, assurance, or validation remains with authorized third parties.