What it writes
Record a scenario saves a planner's working copy of a range as a named diff over the plan on one commitment. It lands as a draft: it changes no buy, claims no prediction and needs no approval. A scenario is never a copy of the plan: a product with no override keeps the plan's depth, and a product taken to nothing is recorded as dropped from the range rather than as a depth of zero. A cash ceiling or an open-to-buy cap is saved as the depths it trims to, one line per product it cuts, so what Settle writes is what the approval applies. Nothing is spent and none of the five declared numbers moves.
A draft that only records an assumption (demand, a cost or price, a shipment shift) has no buy to promote. Settle records it instead: the row reads Recorded assumption, nothing is written to the buy, and it supersedes nothing. An editor may do it, as for a save. A draft that writes to the buy is not recorded this way; it settles through Promote a scenario.
Who may press it
On a plan that includes Commitments, a seat that can write and holds the Commitments editor grant. Combining scenarios and declining a draft take the same grant; promoting and applying take the approver grant. The scenario row above the grid on Buy plan is the act's home. Once something on the working copy has moved, it shows Scenario name (placeholder "Name the scenario"), Edit planned quantities, Save scenario and Review decision. Leave the name blank and the page names it for you: the next number in the list ("Scenario 2"), or the scenario it was revised from with "(revised)" after it. Save scenario stays closed while nothing has moved or nothing has changed since the last save.
Ask Tightly may propose recording a scenario. It reads the commitment, states what it will do, and waits for your Yes or No. Nothing is written until you answer Yes, and the write runs under your own seat:
Record the scenario "{name}" on {commitment name}.
Over MCP nothing here writes: a connected agent reads the commitment, and the act stays a person's press.
What you see
The receipt is one sentence under the row, naming the scenario:
Recorded as “{name}” on the ledger.
The new row then stands in the Scenarios table with the status Draft alternative, the time it was saved and who saved it.
Settle on a what-if that only records ends with its own word, and the row reads Recorded assumption:
Recorded
What to do
There is no delete for a scenario, anywhere, in chat or on the page. The way back is Decline a scenario, which keeps the row with its reason. To back a recorded scenario, Promote a scenario. A working copy that has moved since it was saved has to be saved again before it can be backed, and the backing button says why while it waits:
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.
Refusals you may read
A refused save prints the server's own sentence under the row, and nothing is recorded. A commitment that does not exist is refused as not found. A scenario that is no longer a draft is refused by name and state when Settle tries to record it, and a draft that writes to the buy is refused as not recordable:
This scenario writes to the buy, so it is settled through promote and apply, not recorded.
A scenario carrying more than a hundred distinct product and channel door assumptions, or demand assumptions, is refused with a sentence that names the limit.
A scenario the working copy cannot carry whole reads its own reason in place of Record, with a door to the fuller wall, and a press past it records nothing:
This scenario has what-ifs this page does not show. Open it on the Scenarios wall to change or promote it.
Backing is refused until something is recorded:
Nothing has been recorded yet, so there is no scenario to promote. Record this working copy first.