Work order
What was requested.
Turn a broad public-site polish request into AI-robot-sized work orders for copy, engineering, QA and proof.
Work receipt rec_sample_otto_work_routing
Otto assigned a product polish pass
A manually crafted example receipt showing what a operations ai robot trial should prove.
Operational proof
What actually happened.
This block is safe to share: it records runtime context, scope, cost and mode without exposing secrets.
- Project
- Not recorded
- Runtime / model
- Not recorded / Not recorded
- Mode
- manual_sample
- Cost
- n/a
- Tokens
- n/a
- Duration
- n/a
- Work order
- wo_sample_otto_work_routing
- Run
- run_sample_otto_work_routing · completed
- Risk level
- Not recorded
- Allowed tools
- No tool grant recorded
At a glance
The receipt shape.
A receipt should be readable without knowing the internal workflow.
- Work order
- Turn a broad public-site polish request into AI-robot-sized work orders for copy, engineering, QA and proof.
- AI robot assigned
- Otto · Operations AI Robot
- Checks run
- 3 logged
- Output
- Work routing: Paige: rewrite vague page copy into work-order language. Dex: implement the scoped Rails view...
- Proof
- Timeline has 5 events
- Limit
- Otto routed work but did not replace specialist review.
- Next action
- Human approval required before using this output externally.
Buyer proof brief
Use this receipt before buying more work.
The request, output, checks, limits and approval point a buyer can review before giving the AI robot a larger work order.
- Reusable case-study frame
- Request, AI robot, output, checks, limitations and next action are all visible.
- Review evidence
- 3 steps, 3 checks and 3 limits recorded.
- Next buying decision
- Human approval required before using this output externally.
After this proof
Next ways to inspect Otto.
A receipt should make the next decision concrete: read the resume, compare non-binding pricing examples, inspect the advanced workflow, or send one more small work order for human review.
Basic resume
Read Otto's resume
Best-at work, limitations, required inputs and example first tasks.
Pricing examples
Compare example bands
Non-binding starter bands, work-order shapes and receipt-to-value examples before more spend is approved.
Advanced usage
Inspect the workflow
Run modes, permissions, evidence, guardrails and human handoffs.
Next work order
Send a small job
Use this receipt shape to ask for the next checked piece of work.
AI robot assigned
Otto · Operations AI robot
Otto runs the internal AI robot company and keeps every function moving proactively.
Steps taken
-
1. Read goal
Converted the polish brief into bounded work areas.
-
2. Assigned AI robots
Matched work to Paige, Dex, Frank and Marc.
-
3. Set stop line
Excluded dashboards, accounts, billing and broad marketplace features.
Checks run
Scope
Kept the work to public pages, forms, roster and receipts.
Routing
Assigned specialist AI robots only where their resumes fit the task.
Approval
Marked final copy and commit for human approval.
Output
What came back.
Work routing:
Paige: rewrite vague page copy into work-order language.
Dex: implement the scoped Rails view and seed changes.
Frank: check receipt fields, form behavior and mobile surfaces.
Marc: make the Dex receipt the main proof object.
Approval:
Human owner approves final site copy and commit.
Proof / evidence
What happened.
17:22:24 · received
Task received
The sample work order was logged.
17:23:24 · assigned
AI robot assigned
Otto was assigned to the sample run.
17:24:24 · worked
Output drafted
The manually crafted launch output was produced.
17:25:24 · checked
Checks run
The sample was checked for clarity, limitations and approval notes.
17:26:24 · receipt
Receipt issued
The receipt was stored as a shareable proof object.
Limitations
What is not proven.
Otto routed work but did not replace specialist review.
No billing, accounts or dashboard work was included.
Human approval remains required for the final ship.
Next action
Human approval required before using this output externally.