Skip to content
Dark MatterDark Matter
Energy

Energy & Compute

Register, contract, and transfer compute-ready energy assets — stranded power, permitting, interconnect, and tolling — using the DMTR schema. ComputeSlot decorates Position; the rights engine evaluates BIS, OFAC, RIGI, and permit compliance; CapacityContract captures standard PPA and tolling structures.

What DMTR Energy models

DMTR Energy represents compute-ready energy assets — land, permits, power, interconnect, cooling, and backhaul — as transferable, decomposable, encumberable positions. Operators register assets; tenants discover and contract them through the /v1/energy API and the MCP energy toolset.

Same protocol, different asset class. A Position is the universal legal and economic wrapper. A ComputeSlot is the physical and operational layer that references a Position through the vertical_decoration hook. The rights engine, consent chain, encumbrances, decomposition, and 4(a)(7) secondary-transfer mechanics carry over unchanged from core.

Capabilities

ComponentStatusDescription
ComputeSlot schemaImplemented1 MW atomic unit; decomposable; references a Position via position_id
CapacityContract schemaImplementedPPA, Tolling, Merchant, and Hybrid structures with capacity payment, dispatch authority, fuel supply chain, outage regime, force majeure, and resource adequacy pledge
DemandSpec schemaImplementedStructured tenant RFP matched against slot inventory by the rights engine
Aggregation primitivesImplementedThree-level composition stack: AllocationPlan (ephemeral), CapacityPool (persistent), PoolTranche + waterfall (settlement layer)
StageGate state machineImplementedNine-gate development ladder from LAND through TENANT
Energy rights engineImplementedEight compliance checks: interconnect priority, permit stack, water draw, BIS export controls, OFAC, data residency, RIGI eligibility, indigenous consultation
Settlement mathImplementedMonthly capacity payment with availability and heat-rate adjustment, Adverse Capacity Event detection, day-for-day force-majeure term extension
/v1/energy/* APIDeveloper PreviewSlots, demand, contracts, dispatch notices, jurisdictions, stage gates
Patient Energy ZeroImplementedEnd-to-end reference implementation using the Pampa JV (Vaca Muerta, 200 MW)
MCP tool definitionsImplemented10 energy tools (slot inventory, demand, regulatory corpus, capacity-payment preview, chip SKU) — see MCP energy tools
Canton/DAML settlementPlannedGoldstream node is live; energy bookkeeping integration is downstream

Use cases

  • Asset operators — Register stranded energy (associated gas, curtailed hydro, off-grid wind) as a transferable, securitizable unit visible to AI workloads.
  • Hyperscaler procurement — Query a single registry of compute-ready inventory and match against structured demand specs across jurisdictions.
  • Infrastructure fund managers — Read every project's stage-gate state, permit stack, and tenant assignments as machine-readable objects.
  • Secondary transfers — Reassign capacity between tenants using the same 4(a)(7) playbook DMTR applies to fund interest transfers.

Out of scope

  • Spot-market pricing. DMTR Energy registers assets and executes contracts; price discovery is external.
  • Chip-level allocation. The schema stops at plug-ready megawatts. Rack configuration is the tenant's domain.
  • Regulated utility tariffs. Tolling and merchant generation are in scope; vertically integrated utility billing is not.

Getting started

Edit this page on GitHub

Last reviewed: June 12, 2026

Was this page helpful?