Every article the product writes follows a playbook: the current set of content principles the prompts are built on. The playbook is versioned, and once a quarter the product researches current search guidance and drafts an updated version.
A draft never activates itself. It waits for a human — an admin reviews the draft against the active version and approves or rejects it. Until someone approves, generation keeps using the active version. And if the playbook system is ever unreachable, generation falls back to a built-in static playbook rather than failing.
When to review it
Check the playbook page at the start of each quarter — that's when a new draft appears. Review it sooner if search guidance shifts in a way that matters to your content and you want to know what the writer is currently told.
Review a draft
To review a draft:
- Open
Playbook(admin access). - If a draft is waiting, open it. The page shows a diff versus the active playbook version, so you review what changed, not the whole document.
- Approve to make it the active version for all future generation, or reject to keep the current one. Nothing else is needed — articles pick up the active version on their next run.
How versions are tracked
Each article's stored score carries the playbook version it was written under, so when quality shifts you can tell whether a playbook change is involved. The diff view is the review surface: additions and removals against the active version, in place.
Limits and usage
- Drafts are researched quarterly on a schedule; there's no manual "research now" button.
- Approval is admin-gated. Workspace members can read the playbook but not change which version is active.
- Rejected drafts stay in history — a rejection is a decision, not a deletion.
If something isn't working
No draft appeared this quarter. The research run only drafts when it finds material changes, and it holds off while a previous draft is still waiting for review. An empty quarter usually means nothing changed enough — or the one already pending needs reviewing.
"Failed to load playbook versions." A loading error on the page, not data loss — reload. Generation is unaffected either way because of the static fallback.
You approved a draft and an article still reads like the old rules. Check the article's run time: jobs already in flight finished under the version they started with. New runs use the new version.