What it writes
Decline a scenario records that a scenario was not taken, with a stated reason. The row stays on the ledger with its diff and any recorded prediction, because a declined scenario is the counterfactual Hindsight measures the chosen buy against. It is the one write on this surface that can destroy nothing: there is no delete route, and declining is how a scenario ends. Nothing is spent and none of the five declared numbers moves.
Who may press it
On a plan that includes Commitments, a seat with the Commitments editor grant may decline a draft, and an admin resolves to approver, which includes editor. A chosen scenario or one awaiting approval takes the approver grant, so an editor cannot undo what an approver backed. A scenario sent for review is declined by the person who proposed it (which withdraws it) or by an approver. If proposal review has been switched off for the workspace, any seat that can write may decline any of them. The act's home is the scenario row on Buy plan, with the scenario being worked from loaded: press Review decision, type the reason in the decision note, open Other scenario actions and press Decline. The button stays closed until a reason is typed. Ask Tightly may propose it as decline_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 under the row:
“{name}” is declined and kept on the ledger; the plan of record is unchanged.
In the Scenarios table the row reads Not taken, with the reason on its trail. Declined rows are never hidden from the table. The working copy on the desk is untouched.
What to do
There is no way back and none is needed: a declined scenario is a record, not a loss. To back a different view, Record a scenario and Promote a scenario. Declining a backed scenario takes an approver, so an editor cannot decline one an admin promoted. Nothing is armed by it, and the row survives with its diff and prediction.
Refusals you may read
Before the press, the button's hover says why it is closed:
Nothing is loaded to decline.
This scenario is already declined.
On the server, a scenario that does not exist is refused as not found, and one already declined is refused by name, because declining twice would put a second event in the trail for one decision. A scenario that changed state while you read it asks you to refresh and retry. A decline with no reason is refused, because the reason is what makes the row a counterfactual rather than a discarded draft. A discount scenario is not declined here; it is rejected or withdrawn through its markdown decision.