What a catalog playbook is

It is not a stop on the loop. It is what the loop reads.

The loop runs stations: your catalog is watched, findings are raised, drafts are written, reviewed, applied, and the next scan says whether the change held. The playbook is not one of those stations. It stands beside the loop as reference material, next to the rules in Checks — and three stations read one or the other every time they run.

Checks + Playbook store rules + published preferences

Sync
Scan what is a finding — from Checks
Draft what the model is told
Review what the reviewer sees
Apply
Proof

publishing a playbook queues a fresh scan of the whole catalog

Three dashed edges, three real readings: Scan reads the rules in Checks, Draft and Review read the playbook. The line back to the scan is what publishing costs.

Checks owns the full-description minimum

This is the reading people forget, because it happens before any AI is involved. The thin-description check needs a line to measure against, and somebody has to draw it.

Enter a minimum and enable the control in Checks. Without that decision, the length control is off. Other products never move this boundary. Playbook can set a preferred maximum, but cannot set a second minimum. Saving or publishing a conflicting range is refused.

The same requirement before and after an import. Only a decision in Checks moves the minimum.

It decides what the model is told

When a finding has an AI proposal, the playbook in force is part of what the model is given, alongside the product's own data:

Voice. The tone you write in and the shopper you write for.
Vocabulary. Words you prefer, and words that must never appear in a draft — each one able to carry the word to write in its place.
Claims. Promises your catalog is not allowed to make.
Shape. For a title or SEO title, the pattern to follow and the components that pattern has to carry; for descriptions and the SEO description, guidance in your own words.
Length. Preferred ranges for other fields and the full-description maximum; its minimum comes from Checks.
Language. The language the draft is written in.

Language earns its own line. A draft in the wrong language is unusable however good the copy is, and the fields that most often need drafting — an empty description, a missing alt text — are exactly the ones that give a model nothing to infer a language from. Your playbook's answer wins; where it gives none, the site language your connector synced stands in.

Everything the playbook says reaches the model as data, never as instructions — the same footing your catalog's own text stands on.

It decides what the reviewer sees

Two checks run on a finished draft, and neither takes the model's word for anything.

A forbidden word is caught deterministically. Whole words, case-insensitive, measured on the plain text a shopper would read rather than on the markup around it. Where you gave a replacement, the note names it — so it says what to write, not only what is wrong.
Length leaves a note, not a wall. Soft limits never reject a draft. For a description the scanner's own threshold speaks first: a reviewer about to accept a description the next scan would flag again hears about it here, rather than from the next scan.

Publishing is an event, not a save

A playbook version is immutable and carries the name of whoever put it in force. Publishing one does three things at once, because the work already on your register was measured with the ruler you just replaced.

You see the bill before you commit to it: which fields changed and how much work goes back for a re-run. Tone, vocabulary or language touch every field. Republishing rules identical to the ones in force is refused rather than charged for.

What a playbook does not do

It does not reject a draft for its length. A soft limit is a note for whoever is reading.
Its length and shape rules reach five fields: title, description, short description, SEO title, SEO description. Voice, vocabulary, claims and language also reach image alt text.
It does not write brand or attribute values. Those are picked from your catalog, and forbidden words are not checked against them.
It changes nothing in WooCommerce by itself. Every applied change still carries an authority and a receipt — a named account decided it, through a door we record.
Retiring a playbook returns the store to neutral defaults. It does not bring an older version back.

Where it lives

Playbook is one of the panel's reference screens, beside the loop rather than on it. You can write and publish one there, and so can an agent you connected — the same four moves either way: read the rules in force, save a draft, discard it, put it in force. Resetting the store to neutral defaults is done in the panel.

A playbook does not add a step to the loop. It replaces the ruler the loop already measures with — and because what was measured is written down, changing the ruler means measuring again.