Review and apply proposals

Overview

The review inbox on the Agent page is where everything the agent produces waits. It is grouped by field, so all the Name proposals sit together, and each group can be filtered with All countries when it spans more than one market.

Nothing leaves the inbox on its own. This is the human gate in the workflow.

The inbox

Everything the agent produces arrives in a review inbox, grouped by market. Nothing leaves it on its own.

The inbox is the human gate in the workflow, and it is the only way agent output becomes a draft.

Reading a card

Each card shows what would change, from what to what, and why.

• Metadata cards show the current value beside the proposed one, with an explanation of the reasoning.
• Keyword cards are reviewed word by word: which terms are being added, which are being swapped, and which are being removed without a replacement.
• Screenshot cards show staged variants built from your real screenshots, not mockups of something you do not have.
• Event and product page cards carry the structured content that would go to the store as a draft.

Read the explanation, not just the diff. A keyword that looks strange in isolation often has a reason behind it, and a reason you disagree with is the most useful thing you can find in a review.

Applying and dismissing

Each card carries two controls, at the right-hand end of the row.

• Apply to draft puts the proposed value into your Spek draft. It does not go to the store.
• Dismiss removes the card. Nothing changes anywhere, including your store listing.

There is no edit control on a card. To change the wording, apply it and then edit the field in the editor, where you can see it beside the rest of the listing and against its character limit.

The two arrows beside the Suggestions / Good switcher undo and redo the decisions you make in this session. Undoing an applied keyword row brings the evicted word back into the draft; undoing an applied card restores the value that was there before, unless you edited the field since. The card returns to the inbox, waiting for a fresh decision. Applies that created something on the store — a screenshot set, an event, a product page — cannot be undone this way.

When the indexed metadata review is complete, the inbox explains what happens next. While the approvals are still only a Spek draft, it asks you to publish before measurement starts. Once that metadata reaches the store, it shows a seven-day countdown while Spek measures rank movement.

Event and product page proposals can create a provider draft, but only through a dedicated action you trigger. Even then, the content is not submitted and not made live.

Stale cards

A card is a comparison against the values that existed when it was drafted. If the underlying field changed since, the card is stale, and accepting it would overwrite the newer value with an older comparison.

Spek flags that rather than applying it. Rebase the card onto the current values and review it again, or reject it and let the next run redraft from what is actually there now.

The same applies after you publish: the next run reads the published listing, so its proposals start from reality. See runs and what happens in one.

Common questions