Creative workflows
Claude Fable 5.2 Long Context: Keep Campaign Revisions Traceable
A long conversation can retain an early discount after the team has withdrawn it. More room for history does not tell the model which decision is current. A campaign needs explicit revision authority.
This guide uses documentation reviewed on November 12, 2026 and an illustrative exercise; it does not report a live Fable test. Use Fable on a Claude surface where it is available, then manually carry the approved material into Ciyo.
Quick answer
Keep an append-only revision register with effective decisions, ask for a handoff based on the current approved version, and verify critical facts against original sources. Treat the summary as a working index, not a replacement for the evidence.
1. Give every decision a version and authority
For a fictional winter launch, v1 proposes a discount and v2 removes it. Record the decision ID, date, owner and the exact item superseded. Keep the old note as history with its status clear.
Distinguish a draft idea from an approved change. A later brainstorm does not supersede an approved offer unless the authorized owner says so. Without that distinction, simple chronological ordering can produce the wrong instruction.
2. Ask for a current-state packet
Request approved offer, product references, deliverable list, unresolved questions and superseded items. Require decision IDs next to sensitive facts. Ask the model to report contradictory sources rather than silently selecting the convenient one.
Check the packet against two anchors: the latest approved offer and the accepted product image. Those anchors catch a useful class of handoff errors even when the summary is much shorter than the conversation.
3. Continue through a clear manual handoff
Copy the verified current-state packet into the Ciyo task with the actual source files. Keep old concepts outside the active request or label them as rejected. Review whether the first draft uses the current offer.
For API developers, Anthropic’s current guidance discusses preserved history constraints. Changing stored earlier instructions is different from appending a new decision; follow the official integration documentation for your surface. This editorial worksheet is not an API migration recipe.
Copy and adapt this request
Replace the bracketed fields with your own approved information. The requested output is a draft for review; the example has not been run as a model benchmark.
From [REVISION REGISTER] and [SOURCE PACKET], prepare the current approved campaign handoff. Include decision IDs, exact current offer, accepted source files, deliverables, unresolved questions and superseded instructions. Treat authority and approval status as explicit fields. Do not resolve contradictions silently or reintroduce rejected ideas. End with checks against the original approved facts.Illustrative revision register
These example checks describe acceptance criteria, not observed model results.
| Version | Status | Instruction |
|---|---|---|
| v1 | Superseded | Discount proposed |
| v2 | Approved | No discount; use product launch message |
| v3 | Discussion only | Try another background |
| Handoff | Derived from approved decisions | Retain v2 offer until changed by owner |
Common mistakes and how to recover
Do not call every old message irrelevant; some old product facts still apply. Mark the specific superseded decision.
If a handoff reintroduces the discount, repair the authority register and regenerate the packet before producing more artwork.
Choose a working method and make the handoff
For a solo shop, start with one item and keep the source facts beside the draft. A team should name one approver and keep a dated version so an old comment cannot silently override the current decision. If the input is incomplete, return to the owner of that fact before polishing the artwork.
Use Ciyo for the visual work described here with the controls and models currently offered in your account. Keep the approved copy separately and add exact wording with editable canvas text where needed. A generated picture is a visual draft; inspect its exported file before using it.
Sources and further reading
Primary documentation and related guides used for this article. Availability and controls can vary by account; verify them before beginning your own run.
Frequently asked questions
Does long context guarantee recall?
No. Verify critical facts and use explicit source references; the presence of material in a conversation is not proof it was applied correctly.
Can I replace the source files with a summary?
Keep the originals. A summary is useful for navigation and handoff but can omit exceptions or uncertainty.
Is this an automatic Ciyo conversation import?
No. The described transfer is manual and includes a human check of the current facts.
Prepare one visual draft in Ciyo
Bring the approved inputs and review one version against the checks in this guide before making more variants.