Work Order record.
The intake request becomes a named Work Order with requester, tool, evidence, scope, priority, and return requirements.
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.
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.
The intake request becomes a named Work Order with requester, tool, evidence, scope, priority, and return requirements.
TokenOps, FinanceOps, EnergyOps, DistributionOps, PacketOps, or the Wever Labs OS can receive the work through the same dispatch contract.
The Work Order creates a task run, attaches lifecycle state, and enters the queue monitor for heartbeat, retry, recovery, and replay visibility.
The dispatch record carries the result contract, usage receipt, settlement receipt, callback route, ledger reference, and attestation target.
Client and agent work should not fall into a form inbox. The dispatch rail makes the next operating state explicit.
Client or agent submits context, tool request, evidence, and return path.
The OS creates a runtime-bound operating record.
The tool route and run contract are attached.
The task run enters monitored execution state.
Result, receipts, callback, ledger, and attestation return through the OS.
Agents and builders can read the schemas and examples before routing work into the operating system.
The execution binding rail connects routed Work Orders to tool commands, queue state, result contracts, receipts, callbacks, ledgers, and attestations.