Redacted Evidence Pack

This packet is the drill-down behind the public case study on /case-study. It shows how the same totals move from source activity rows to factor provenance, immutable ledger entries, approval states, and export reconciliation. Values are redacted or summarized where customer-sensitive detail would normally appear.

24
Activity rows in batch
2
Factor regions locked
4
Approval states recorded
0.00%
Export drift

What This Proves

Source rows can be tied to exact meters, regions, and reporting periods.
Replay of the same import batch does not create duplicate records.
Emission factors are versioned, region-specific, and locked into a factor snapshot.
Calculated totals reconcile to exported totals through a deterministic checksum.
Approval, export, and deletion flows produce durable machine-readable records.
The public case study numbers can be traced back to activity-level evidence.

1. Source Activity Register

Excerpt from the 24-row activity batch used for the public case study totals.

RecordSourceMeter / ConnectorPeriodRegionQuantityQuality
act-office-2026-01utility_bill_csvCAMX-HQ-012026-01CAMX3,112 kWhmeasured
act-office-2026-02utility_bill_csvCAMX-HQ-012026-02CAMX2,984 kWhmeasured
act-cloud-2026-01aws_cost_and_usageNWPP-AWS-012026-01NWPP4,406 kWhmeasured
act-cloud-2026-02aws_cost_and_usageNWPP-AWS-012026-02NWPP4,212 kWhmeasured
Annual Office Rollup
36,556 kWh x 0.225 kg CO2e/kWh = 8.22 tCO2e
Annual Cloud Rollup
52,155 kWh x 0.252 kg CO2e/kWh = 13.14 tCO2e

2. Import Replay and Duplicate Protection

Import batches use stable idempotency keys so retries do not create duplicate activities or duplicate ledger rows.

BatchRunRows receivedAcceptedDuplicatesRejectedIdempotency proof
imp-2026-02-03-001Initial import242400utility_bill:CAMX-HQ-01:2026-01
imp-2026-02-03-001-replayReplay of same file240240same keys reused; no new ledger rows created

3. Anomaly-to-Action Example

One alert from the same reporting workflow, shown here to demonstrate assignment, comments, review, and closure.

Alert snapshot
Alert IDdq-2026-02-014
Categorysudden_change
Severityhigh
Source recordact-cloud-2026-09
Expected3,210 kWh
Actual5,182 kWh
Deviation+61.4%
Resolution trail
Detected
dq-2026-02-014 · sudden_change · Cloud electricity +61.4% vs trailing 3-month average
Assigned
owner = operator@company.com · status = in_progress
Commented
AWS billing export confirms one-time model training workload in September 2026
Reviewed
manager@company.com accepted explanation and kept the record in scope
Outcome
Marked valid, alert closed, totals unchanged, audit log retained

4. Factor Provenance and Snapshot Lock

Factors are stored with source metadata and then frozen into a period-specific snapshot for reproducibility.

Factor IDSourceRegionValueValidityLocked snapshot
grid-camx-2023EPA eGRID 2023CAMX0.225 kg CO2e/kWh2023-01-01 to 2026-12-31snap-q1-2026-001
grid-nwpp-2023EPA eGRID 2023NWPP0.252 kg CO2e/kWh2023-01-01 to 2026-12-31snap-q1-2026-001
Snapshot snap-q1-2026-001 was locked by cfo@company.com on 2026-02-04T11:00:00Z. After this point, the report remained reproducible even if a newer factor release became available.

5. Immutable Calculation Ledger

Each calculation stores the activity reference, factor used, formula, result, actor, and timestamp.

Ledger IDActivityFormulaResultActorTimestampState
calc-camx-annual-202636,556 kWh office electricity36,556 × 0.2258.22 tCO2eoperator@company.com2026-02-03T14:22:00Zdraft
calc-nwpp-annual-202652,155 kWh cloud electricity52,155 × 0.25213.14 tCO2eoperator@company.com2026-02-03T14:23:00Zdraft

6. Approval Trail and Export Reconciliation

Ownership and status changes stay visible through preparation, review, approval, and export.

1
Prepared
Imported 24 monthly activity records and reviewed factor selection.
operator@company.com · 2026-02-03T14:30:00Z
2
Reviewed
Confirmed line items against utility invoices and cloud billing export.
manager@company.com · 2026-02-04T09:15:00Z
3
Approved
Approved for stakeholder review and locked factor snapshot snap-q1-2026-001.
cfo@company.com · 2026-02-04T11:00:00Z
4
Exported
Generated stakeholder PDF and checksum for reconciliation.
cfo@company.com · 2026-02-04T11:06:00Z

Export Record

Report typecalifornia
Purposestakeholder_review
Scope 1 at export0.00 tCO2e
Scope 2 at export21.368160 tCO2e
Scope 3 at export0.00 tCO2e
Total at export21.368160 tCO2e
Checksumb7fd1f798bcfe0b67d43496696a2e52e
Reconciliation result: checksum match = true, drift = 0.00%, on-screen totals equal exported totals.

7. Governance Execution Proof

The same governance APIs documented in the trust center return machine-readable export and deletion metadata.

GET /api/governance/export

Returns exported_at, tenant_id, tenant_name, users, activities, calculation_ledger, and change_log in one JSON package.

"exported_at": "2026-02-04T11:08:00Z"
"tenant_id": "tenant-demo-001"
"tenant_name": "Redacted SaaS Co."
"activities": 24 line items
"calculation_ledger": 24 immutable entries

POST /api/governance/delete-request

Admin-only. Starts a 30-day retention window and records the request in the change log before permanent deletion.

"status": "deletion_requested"
"retention_days": 30
"deletion_date": "2026-03-06"
"message": "Export your data before deletion via GET /api/governance/export."

Pages That Reuse This Evidence Pattern

Each of these pages routes buyers back to the same public proof assets before they ever start a trial.