OIDF

Contracts for commissioning evidence and handoff.

Open Infrastructure Deployment Format - portable schemas for equipment state, typed evidence, SAT gates, and an immutable handoff ledger inspectors can replay offline.

Critical infrastructure still hands off through PDFs, spreadsheets, and click-to-complete workflows. OIDF replaces ad hoc artifacts with a portable format: deterministic state machines, typed evidence, and a handoff ledger that survives air gaps and personnel turnover.

Architecture packs map the format onto deliverable shapes (for example EV depot behind-the-meter, island microgrids, and remote resilient sites) with SAT sequences and safety gates expressed as contracts, not tribal knowledge. Validators and worked example packs illustrate the format.

OIDF is the specification: portable state machines, typed evidence, and a handoff ledger. Keel enforces it; field tooling validates and exports it. The format defines what evidence must exist for a state transition to be attributable.

Enforcement and offline advance live in the runtime.

Continue to Keel →

See the format in motion

A read-only explorer makes the vocabulary legible before a team opens a schema.

Diagram showing OIDF contracts flowing through Keel validation into an exportable handoff bundle
Conceptual boundary: OIDF defines the contract; Keel validates it; the handoff remains inspectable.
01

Choose a machine

Compare the canonical lifecycle, a BESS skid, or a solar inverter path.

02

Inspect evidence

See which typed evidence classes unlock a transition and which source owns them.

03

Follow the handoff

Trace accepted, rejected, and authoritative events without advancing any real asset.

Presentation only; OIDF schemas remain normative and Keel remains runtime authority.

Open the commissioning explorer →