Dispatch rail

Intake becomes a routed Work Order.

Wever Labs OS receives client or agent-submitted context, creates a runtime-bound Work Order, selects the operating tool, opens a task run, and sends the work into the queue with return paths already attached.

What dispatch does

The OS turns submitted context into operating state.

The dispatch rail binds the intake request to a Work Order, runtime record, selected tool, run contract, queue state, result contract, receipt requirements, callback route, ledger path, and attestation target.

Create

Work Order record.

The intake request becomes a named Work Order with requester, tool, evidence, scope, priority, and return requirements.

Route

Tool selection.

TokenOps, FinanceOps, EnergyOps, DistributionOps, PacketOps, or the Wever Labs OS can receive the work through the same dispatch contract.

Run

Task and queue state.

The Work Order creates a task run, attaches lifecycle state, and enters the queue monitor for heartbeat, retry, recovery, and replay visibility.

Return

Proof and delivery paths.

The dispatch record carries the result contract, usage receipt, settlement receipt, callback route, ledger reference, and attestation target.

Dispatch flow

One rail from intake to execution.

Client and agent work should not fall into a form inbox. The dispatch rail makes the next operating state explicit.

01Intake

Client or agent submits context, tool request, evidence, and return path.

02Work Order

The OS creates a runtime-bound operating record.

03Dispatch

The tool route and run contract are attached.

04Queue

The task run enters monitored execution state.

05Return

Result, receipts, callback, ledger, and attestation return through the OS.

Callable contracts

The dispatch rail is available to agents and clients.

Agents and builders can read the schemas and examples before routing work into the operating system.

Execution binding

Work Orders move into operating-tool execution.

The execution binding rail connects routed Work Orders to tool commands, queue state, result contracts, receipts, callbacks, ledgers, and attestations.