Project context enters the OS.
Utility territory, project reference, capacity, site-control evidence, diagrams, application artifacts, milestone records, correspondence, and known gaps bind to a Work Order and runtime record.
EnergyOps controlled pilot execution
One interconnection packet Work Order runs through the OS proof trail.
Controlled Pilot Execution advances an EnergyOps packet readiness review from intake and Work Order dispatch into execution command, evidence checklist, readiness result, result contract, receipts, callback delivery, ledger, and attestation.
{
"pilot_id": "energyops_controlled_pilot_001",
"tool": "energyops",
"execution_mode": "controlled_pilot",
"runtime_state": "ready_for_operator_review",
"proof_trail": [
"work_order",
"execution_command",
"evidence_checklist",
"readiness_result",
"result_contract",
"usage_receipt",
"callback_delivery",
"ledger_entry",
"attestation"
]
}
Operating purpose
The pilot proves EnergyOps can carry project evidence through the same OS rails.
The controlled pilot route names the records the OS writes, the packet evidence EnergyOps checks, the gaps it identifies, the readiness package it returns, and the proof objects an agent or client can inspect.
EnergyOps receives the command.
The operating tool receives a scoped command with packet context, evidence references, readiness criteria, callback target, proof requirements, and review controls.
Packet evidence is checked.
Applications, diagrams, site-control records, study artifacts, fee references, permit references, correspondence, and unresolved items resolve into readiness status and exceptions.
Proof comes back through the OS.
The result contract binds the readiness output to evidence checklist, receipts, callback state, ledger reference, attestation, and operator review.
Pilot sequence
One path carries interconnection evidence from packet review to returned proof.
The route is intentionally narrow: execute one EnergyOps packet readiness review, persist the state, return the proof envelope, and make the run inspectable before expanding workflow volume.
Validate
Check authorization, tool scope, schema version, callback URL, project context, and required evidence references.
Create
Create the pilot record, Work Order binding, execution command, and step events.
Check
EnergyOps reviews packet evidence, milestone records, missing items, stale records, and exception-prone gaps.
Return
Create result contract, usage receipt reference, callback delivery event, ledger entry, and attestation.
Review
Expose the pilot report for console inspection, missing-item handling, replay, and offer readiness.
Activation path
EnergyOps controlled pilot execution proves the OS rails for project evidence readiness.
TokenOps proves the tokenized-asset path. FinanceOps proves financial reconciliation. EnergyOps proves interconnection packet and evidence readiness through the same intake, execution, return, callback, ledger, and attestation rails.