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 style with no override keeps the plan's depth, and a style taken to nothing is recorded as dropped from the range rather than as a depth of zero. Nothing is spent and none of the five declared numbers moves.

Who may press it

A seat that can write, on a plan that includes Commitments. The scenario row above the grid on Work the buy is the act's home: it opens once something on the working copy has moved, a kept scenario is being worked from, or a comparison is open. Type a name, or leave it blank and the row names it for you (the next number in the list, or the scenario it was revised from with "(revised)" after it), then press Save scenario. The button stays closed while nothing has moved or nothing has changed since the last save. Ask Tightly may propose it as record_commitment_scenario; pressing the chip asks Ask Tightly to restate the act, your yes is the confirm, and the write then runs under your own seat. 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. Its Details drawer holds the trail, the one record of author, reason and what later happened to it.

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 carrying more than a hundred distinct style 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.