What it writes
Promote a scenario backs a recorded scenario and records its prediction. A diff inside the envelope lands promoted: it is the buy being made, and the system declines the scenario before it and keeps it as the counterfactual. A diff that moves or newly declares the envelope, a buy over a declared envelope, or a buy that cannot be checked against it goes for approval if your approval settings require a second admin. A buy cannot be checked where it could not be priced, a placed order line has no unit cost, the commitment is rolling (a monthly rate), or a channel shock cannot be split by channel in full. Where one admin may sign alone, it lands promoted with every reason recorded, and a changed envelope still arms nothing until you amend the commitment. A scenario that goes to approval supersedes nothing: the running scenario keeps the buy until somebody signs.
Promoting submits no declaration and approves no buy version. Settling a what-if in the Scenarios workspace promotes it and then applies what it writes to the buy. The apply is checked first: a write that takes open-to-buy short, or puts the buy over the envelope, is refused and the scenario stays a draft. A scenario that writes nothing to the buy (demand, a cost or price, a shipment shift) is recorded from Settle instead, as in Record a scenario.
Who may press it
A seat with the Commitments approver grant, admins included; with proposal review off for the workspace, any admin. On Buy plan, press Review decision on a scenario row. The backing button reads Choose this scenario or Record approval required, according to your approval settings, and its hover names the reason. The working copy supplies the prediction.
Ask Tightly may propose it for an admin seat. It reads the scenario, states what promoting would do, and waits for your Yes or No. Nothing is written until you say Yes. The sentence says the prediction is supplied and not independently verified, and that promoting records a scenario decision only and does not apply quantities or prices, approve a buy version, or create Bench lines or purchase orders. Over MCP nothing here writes; the act stays a person's press.
What you see
The receipt under the row names the outcome:
“{name}” is recorded as the chosen scenario.
“{name}” is recorded as requiring approval.
Chosen over the envelope, the receipt adds why:
Promoted over the envelope. Your approval settings let one admin choose it, so it was not sent for approval.
In Scenarios the row then reads Chosen decision or Awaiting approval, and a superseded scenario reads Not taken, with "Replaced by a later scenario" in its trail. Settle ends in one line: "Settled. Committed v{n}. Wrote {counts}", "Recorded" for an assumption that wrote nothing, or "Not applied. {reason}" where it was backed but the buy was untouched.
What to do
The way back is to promote another scenario, which supersedes this one and keeps it, or to Decline a scenario with a reason. A promotion is never removed from the ledger. An unrecorded view is saved first with Record a scenario.
Refusals you may read
Before the press, the button stays closed and says why:
This has changes that are not on the ledger yet. Record it first — a promotion is a claim about a scenario that exists, and there is nothing yet to make the claim about.
Nothing has been recorded yet, so there is no scenario to promote. Record this working copy first.
This scenario has already been decided. Record a new one rather than backing this one twice.
This scenario has what-ifs this page does not show. Open it on the Scenarios wall to change or promote it.
Settle refuses in a sentence of its own, and nothing is written:
Already settled: another scenario was backed first. Nothing was written. Open it again to decide against the buy as it stands.
The backed scenario is already in the buy, so it stays. Nothing was written.
Not settled: applying this leaves open-to-buy {left} short (live: {live} left). Make room within the OTB first.
A discount scenario cannot replace the buying scenario:
Submit this discount for markdown approval; it cannot replace the buying scenario.
Where two promotions reach the slot in the same instant, the second ends:
Only one scenario at a time may be the buy that is being made.