Work Order source.
Client or agent intake resolves into a Work Order, tool route, runtime record, and execution binding.
TokenOps controlled pilot execution
One TokenOps Work Order runs through the OS proof trail.
Controlled Pilot Execution advances a TokenOps task from intake and Work Order dispatch into execution command, runtime state, result contract, receipts, callback delivery, ledger, and attestation. The pilot path is designed for supervised activation, console review, and repeatable proof.
{
"pilot_id": "tokenops_controlled_pilot_001",
"tool": "tokenops",
"execution_mode": "controlled_pilot",
"runtime_state": "ready_for_operator_review",
"proof_trail": [
"work_order",
"execution_command",
"result_contract",
"settlement_receipt",
"usage_receipt",
"callback_delivery",
"ledger_entry",
"attestation"
]
}
Operating purpose
The pilot creates one inspectable run instead of another reference diagram.
The controlled pilot route is the bridge between public contracts and a supervised operating run. It names the records the OS writes, the execution command the tool receives, the result package the tool returns, and the proof objects the requesting agent or client can inspect.
Tool command.
TokenOps receives a scoped command with task token, requested capability, evidence inputs, callback target, and proof requirements.
Result contract.
The result contract binds the TokenOps output to settlement receipt, usage receipt, callback state, ledger reference, and attestation.
Console visibility.
The console can inspect runtime state, retry state, callback delivery, receipt status, and proof envelope readiness.
Pilot sequence
One path carries the work from request to returned proof.
The route is intentionally narrow: execute one TokenOps task, persist the state, return the proof envelope, and make the run inspectable before expanding to additional workflow volume.
Accept
Validate identity, tool scope, callback URL, schema version, and required TokenOps evidence.
Create
Create the pilot record, Work Order binding, execution command, and step events.
Execute
Advance TokenOps runtime state and return a result package with status, exceptions, and next action.
Return
Create result contract, settlement receipt reference, usage receipt, callback delivery event, ledger entry, and attestation.
Review
Expose the pilot report for console inspection, retry/replay decisions, and offer readiness.
Activation path
Controlled pilot execution is the first operating run to carry real state.
The OS has the public contracts, runtime tables, auth boundary, callback rail, and service-role policy pack. This pilot binds those pieces into one supervised TokenOps run.