The useful result
Match every requested deliverable to a real output or an explicit blocked status.
- Match every requested deliverable to a real output or an explicit blocked status.
A long final message can emphasize the last asset and overlook something requested earlier. Before a multi-part task, define a small deliverable manifest with names and acceptance checks. This lesson focuses on a client-ready handoff: a summary, an email and a checklist, rather than code migration or an autonomous publishing workflow.
Fable 5.1 requires eligible paid access; plan inclusion and usage credits differ. Check the linked account guide. You can practise the technique on the supplied fictional inputs with an available compatible assistant first. This lesson is documentation-based; examples are expected results, not a claim that we ran the named model.
Before you start
- A fictional brief requiring three distinct assets.
- A visible acceptance rule for each asset and a place to inspect the actual outputs.
Review evidence
Documentation-based review · 2026-10-18
Provider documentation checked on 18 October 2026. Examples and checks are original illustrative exercises, not recorded platform tests. Cover artwork is conceptual and does not imply provider sponsorship.
Write the acceptance rows first
Use D1=50-word summary preserving price and license; D2=short email with one real link placeholder; D3=five-point QA checklist. Decide whether these are text blocks or actual files. A filename in a message is not proof that a file exists.
Example / expected result
Illustrative example; not a recorded model result.
D1 summary; D2 email; D3 checklist. Each must have its own output location and READY/BLOCKED/NOT STARTED status.
Check your result
All three asset IDs have a unique format and check.
Ask for the manifest alongside the work
Require the model to complete the assets and report their real location or section. If an input is missing, it should state the limitation rather than invent it. Do not let the manifest replace the requested content.
Create D1 summary, D2 email and D3 five-point QA checklist from the supplied fictional brief. Preserve stated facts. Finish with asset ID, output section or actual file, status and acceptance evidence. Never mark a missing file or empty section READY. Use BLOCKED with a reason when needed.Example / expected result
Illustrative example; not a recorded model result.
Illustrative partial handoff: D1 READY in Summary; D2 BLOCKED because destination URL is missing; D3 READY in Checklist. No file creation is claimed.
Check your result
Each READY row points to an output you can actually inspect.
Reopen the outputs
Read each text section or open each downloadable file. Check counts and protected facts yourself. Resolve blocked items by supplying the missing input, then ask for only that asset so accepted work does not drift during a full rewrite.
Check your result
The manifest reflects inspected outputs; incomplete work is not described as a finished package.
When it goes wrong
A manifest can contain false completion claims. It is an inspection aid, not evidence by itself. Do not authorize sending, posting or client delivery merely by asking for a draft package.
Make it your own
Remove the email from a completed sample while leaving its READY row. Your review should catch the mismatch and change D2 to missing before handoff.
Useful next resources
Sources and review
Last checked Oct 18, 2026. Features and account limits can change. Verify important results against your original material.
Did this help you complete your task?
Tell us what needs improving. No account or private output required.
Report incorrect information or a broken linkGenius Forges Editorial
Practical AI lessons with checked sources, labelled examples and human verification.
