Work Orders
A Work Order keeps autonomous work bounded: request, plan, execution, proof, memory trace, and final outcome stay together. In the tour, the queue is anchored by the real golden run.
Follow the path: start work, observe execution, inspect proof, then understand cost, compliance, and controls.
MRL-2026-0047: Production UI smoke-test note
The tour uses this completed production run as the reference thread, so each page shows a different lens on the same request, PR, audit bundle, and cost record.
Work Order
MRL-2026-0047
archived
Pull request
#317
github.com/bmozi/merlin/pull/317
Audit bundle
257 entries
digest f35fee0f04ab
Cache reuse
1.35M
$21.15 avoided
Proven
check or signed artifact
Observed
event or runtime signal
Claimed
agent statement only
Review
human judgment required
Sample Work Order queue
The command center for scoped implementation runs.
Operator action bar
Controls look real so guests understand the workflow, but live mutation paths stay locked.