Scattered sources
Meter reads, ERP exports, and supplier files live in email threads and shared drives with no single knowledge time.
Dahlia Carbon Intelligence
DCI
Turn fragmented carbon data into decisions you can verify.
DCI connects operational data, evidence, calculations, and review workflows in one traceable system — so operators and verifiers stop chasing spreadsheets and start from the same sealed record.
The operational problem
Carbon work fails in the handoffs.
Most delay is not the calculation itself — it is missing evidence, unclear history, and repeated requests between the plant team and the verifier.
Untraceable claims
A number appears in a report without a durable link to inputs, methodology version, or who changed what later.
Review thrash
Verifiers ask for the same documents again because the package does not carry the body and the hash together.
Last-minute pressure
Corrections after declaration day collide with “what we knew then” — unless valid time and knowledge time stay distinct.
How DCI works
One chain. Clear next action.
From facility data to sealed evidence to independent review — without silent ledger writes.
Collect & organize
Measurements and documents enter with provenance. Proposals stay staged until a human commits.
Calculate & understand
Methodology packs evaluate to value, unit, and lineage hash — reproducible offline.
Review & verify
Sealed bundles open in the verifier portal under grant scope — read, not rewrite.
Act & report
Findings, attestations, and exports stay tied to the same merkle root.
Who it is for
Two workspaces. Same record.
Operator runs the ledger. Verifier reviews sealed evidence independently.
Operator
Facility and compliance teams who record measurements, run calculations, seal bundles, and respond to findings.
- Ledger, facilities, calculations
- Seal & distribute evidence packages
- Human commit for staged proposals
Verifier
Accredited reviewers who need grant-scoped access to sealed packages — download, inspect, and attest without operator write rights.
- Grant-bound portal access
- Offline-verifiable packages
- Client-side attestation signing
Capabilities
What the product actually does
Mapped to shipped surfaces — not a feature wishlist.
Bitemporal measurements
Valid time and knowledge time stay distinct. Corrections append; they do not erase what you knew on declaration day.
Reproducible calculations
Methodology packs hash into every result. Same inputs and knowledge time → same output, offline.
Sealed evidence bundles
Merkle-rooted packages carry lineage, documents, and attestation hooks for the verifier portal.
Staged intelligence
Extraction proposals land off-ledger. The ledger changes only when an operator commits — never by silent write.
Tenant isolation & MFA
Organization-scoped access with RLS; sensitive actions require MFA-satisfied sessions where enforced.
Why trust the result
Evidence over theatre
Append-only core
Measurements and calculations do not silently mutate. Supersession is explicit.
Offline verification
Package bodies recompute hashes and merkle roots without requiring our servers.
Least privilege
Verifier grants are scoped. Private attestation keys stay on the client.
Compliance claims
SOC 2 / certifications · not claimed here — readiness artifacts only when published by the business.
Local rehearsal
Walk the chain without writing the ledger
Scripted demo only — no live model API. It narrates measure → resolve → calculate → findings → seal.
Real work happens under /app.
Honest demo: responses are scripted locally. They are not model completions.
Rehearsal output
Submit a note to see stages: measure → resolve → calculate → findings → seal.
Developers
HTTP first. Packs as code.
Operator and verifier surfaces sit on the same Fastify API. The methodology id below is a real pack in-repo.
// Bearer API key · tenant set by key curl -s /v1/calculations \ -H "authorization: Bearer $DAHLIA_KEY" \ -H "content-type: application/json" \ -d '{ "facilityId": "…", "methodologyId": "cbam/aluminium-extrusion", "productionDate": "2026-08-18", "periodFrom": "2026-08-01T00:00:00Z", "periodTo": "2026-09-01T00:00:00Z", "knowledgeTime": "2026-08-20T12:00:00Z", "inputs": { "natural_gas_volume": { "measurementIds": ["…"] }, "billet_mass": { "value": "2", "unit": "t", "provenance": "erp" }, "production_mass": { "value": "2", "unit": "t", "provenance": "erp" } } }'
Start where the work already is
Open the operator ledger or the verifier portal. Same evidence chain — different duties.