Skip to main content
Help Center
Getting started 4 min read·Updated Jul 6, 2026

Promoting a dry-run decision to live, one row at a time

New stores run dry by default — agents decide, nothing executes; promote single rows to live and enable automation areas as the record earns trust.

New stores start in dry-run / approval-only mode: agents decide, but nothing executes until you promote it. In dry-run, the full loop executes — planner proposes, judge scores, everything is logged — but nothing touches your store. Each row shows exactly what would have happened: the action, the subject, the evidence, and the state transition it would have made.

app.magistry.io/dashboard/decisions
The Decisions feed listing applied and dry-run decision rows, each with its trigger and a revert action
The Decisions feed — applied rows and dry-run rows side by side, every applied action revertible.

Promoting a single row

  1. 1Open the Decisions page and filter to dry-run rows.
  2. 2Pick a row you agree with. Read its evidence chain — the point is to promote decisions you've actually verified, not decisions that merely look plausible.
  3. 3Click Promote. The action executes for real — and stays revertible, since the revert executor can derive the undo from the row's action — with the live row linked back to the dry-run row it came from.

Row-level promotion is the smallest possible unit of trust. You're not turning on a category of automation — you're executing one decision you've personally read. Early on, this is how most live actions should happen.

Promoting an automation area

Once the dry-run record for an action type is consistently right — the rows stopped surprising you days ago — you can enable that whole area for live execution instead of clicking row by row. This is per action type, not global: catalog copy can run live while price moves stay dry indefinitely.

The 14-day shape

The dry-run→live playbook takes about 14 days to full autonomy for most stores: a week of reading rows daily, then a week of promoting areas as each earns it. Rushing it moves your surprises from the dry-run log into production. The boredom of reading correct rows is the signal you're ready.

Promote the row after you've read the evidence, not after you've read the title.

// still stuck?

Talk to a human who knows your store.

Live chat Mon–Fri 09:00–18:00 CET, email with a 24-hour SLA, or a 30-minute call. Support reads the same decision_log you do.

Free to read · No email gate · Versioned with the platform