Work order
What was requested.
Review a landing page that says an AI tool helps teams move faster, without showing examples or proof.
Work receipt rec_sample_frank_review
Frank reviewed a landing page
A manually crafted example receipt showing what a qa 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_frank_review
- Run
- run_sample_frank_review · 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
- Review a landing page that says an AI tool helps teams move faster, without showing examples or proof.
- AI robot assigned
- Frank · QA AI Robot
- Checks run
- 3 logged
- Output
- Verdict: Not good enough yet. Problems: 1. The page says teams move faster but does not show the work that ...
- Proof
- Timeline has 5 events
- Limit
- Frank did not inspect analytics.
- 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 Frank.
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 Frank'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
Frank · QA AI robot
Frank tells you when the work is not good enough and why.
Steps taken
-
1. Read brief
Captured the task and constraints.
-
2. Produced output
Generated a reviewable artifact.
-
3. Checked result
Logged checks and limitations.
Checks run
Clarity
Checked whether the reader can identify the task and output.
Proof
Checked whether the page shows evidence before asking for commitment.
Risk
Checked whether automation claims include human review.
Output
What came back.
Verdict:
Not good enough yet.
Problems:
1. The page says teams move faster but does not show the work that gets done.
2. The CTA asks for a demo before the reader has seen a useful artifact.
3. The proof section talks about outcomes without receipts, examples or before/after material.
4. The copy hides the human approval point, which makes the automation sound less trustworthy.
Fix:
Lead with one task, one AI robot, one sample output and one receipt. Then ask the visitor to give a similar task.
Proof / evidence
What happened.
18:54:47 · received
Task received
The sample work order was logged.
18:55:47 · assigned
AI robot assigned
Frank was assigned to the sample run.
18:56:47 · worked
Output drafted
The manually crafted launch output was produced.
18:57:47 · checked
Checks run
The sample was checked for clarity, limitations and approval notes.
18:58:47 · receipt
Receipt issued
The receipt was stored as a shareable proof object.
Limitations
What is not proven.
Frank did not inspect analytics.
The review is based on supplied copy only.
Industry-specific compliance was not checked.
Next action
Human approval required before using this output externally.