Review before publishing

Every AI tool in Fenómenus stops before saving. This page is what to do in that pause, and why the pause exists.

The pause is deliberate

• The wine search fills a record you then read.
• The bulk enhancer shows a batch you approve.
• The photo import produces rows you edit.
• The description writer fills a field.
• The translation action fills a form.

In every case the last action is yours. That is the product's position: these tools draft, you decide.

Why generated text needs more review, not less

The failure mode is not obvious nonsense. It is fluent, confident, plausible text that happens to be about the wrong wine, or to contain an ingredient nobody put in the dish.

Errors that look like errors get caught. Errors that look like good writing do not.

The review, by tool

Wine records — verify five identity fields against the physical bottle: producer, cuvée, vintage, region, grape. If any is wrong, the record describes another wine. Then read the description and the tasting notes as a guest.

Photo imports — check the row count against the page, and every price against its column. A glass price read as a bottle price is the expensive error here.

Descriptions — check that no ingredient appears that was not in your brief. Cut the length. Remove generic praise.

Translations — check that proper names survived, that the length matches the source, and that terminology is consistent.

The allergen rule

No AI tool assigns allergens, and no generated description should be treated as an allergen statement.

If a generated description mentions an ingredient, that is not the same as the dish declaring an allergen. Allergens are assigned per item, from the recipe, by a person. See Assign allergens to items.

Batch sizes you will actually finish

The practical limit is attention, not credit:

• wines — twenty to fifty per batch;
• descriptions — one section at a time;
• translations — one section at a time.

A batch too large to review is not a productivity gain. It is unreviewed content on a public menu.

A realistic standard

You do not have to rewrite everything:

• Verify every identity fact — which wine, which dish, which ingredients.
• Read everything that will be published.
• Rewrite what sells: the by-the-glass wines, the recommendations, the featured dishes.
• Accept routine detail on items guests rarely ask about.

After saving

1. Spot-check ten items against reality.
2. Confirm nothing you had curated by hand was replaced.
3. Confirm prices are unchanged — no tool sets them.
4. Confirm allergens are still correct.
5. Read the section signed out, on a phone.
6. Regenerate any PDF in circulation.

The standing rule

Anything a tool produces is a draft until a person has confirmed it. Fenómenus enforces the pause; the judgement is the part that cannot be automated, and it is what your guests are actually paying for.