Layer 02 · Transform

The allocation engine

Connects verified performance to commodity flows via mass balance, supply-shed attribution, and chain of custody — so the number survives blending, processing, and every change of hands.

Get your readiness review

Layer 02 · Transform

The allocation engine

Connects verified performance to commodity flows via mass balance, supply-shed attribution, and chain of custody — so the number survives blending, processing, and every change of hands.

Get your readiness review

01 — What the engine does

From verified performance to a portable number.

01

Mass balance

Allocate verified intensity across pooled volumes so credits track physical throughput, not paperwork.

02

Supply-shed attribution

Tie performance to the geographic supply shed it came from, with defensible boundaries and overlap rules.

03

Chain of custody

Carry provenance through every custody event — blending, processing, storage, and transfer.

04

Survives transformation

The number persists through processing and change of hands, so downstream claims stay intact.

02 — How allocation works

Evidence in, an allocation-aware object out.

01 · Intake

A normalized MRV object enters from the ingest layer with full provenance attached.

02 · Attribute

Performance is matched to a supply shed and apportioned across pooled volume by mass balance.

03 · Carry

Each custody event updates the ledger so intensity follows the physical commodity downstream.

04 · Hand off

A transformed, allocation-aware object is passed to the audit and clearing layer.