The sentence
On Declare, the Review step runs a dry run of the declaration. While it runs, the line beside the buttons reads:
Checking the declaration against your book.
Where the dry run refuses, the reasons appear above Declare commitment, joined with " · ", and the sentence beside the buttons reads:
Refused, and nothing was written.
Where the dry run could not be read, the page says so and adds that this is a failed read, not a refusal, and nothing is compiled. A compiled answer adds no sentence of its own: What Tightly will build is the answer.
What it means
Before a declaration is recorded, Tightly compiles it. The dry run binds each declared number to the engine that will defend it, against your book as it stands, and writes nothing whatever it answers. A refused compile is a full answer, not an error: the compiler could not honestly bind the scope, and it says why instead of approximating. Reasons it can give include a category that does not exist, no live buy plan season over the window, a scope whose share basis cannot be measured, and a budget no category's funds can cover.
Only a compiled answer opens Declare commitment and Save as draft (both record the same awaiting-approval commitment). Checking, failed, unreadable and refused all leave them closed. So does a compiled answer whose category funding check does not pass; in that case the check's own reason prints beside the buttons.
A number that is not fully bound is not always a refusal. A budget that some categories can fund and others cannot is Partial: it reserves what it can and names the legs it could not bind, each with its reason and amount. A number nobody declared is Unbound: nothing was asked of the engine, so it is an absence, not a refusal and not a zero budget. A binding no engine can make is Unavailable. These show in What Tightly will build as engines not armed in full, and as tasks such as "Finish the buying budget".
What to do next
Read the reasons; they name what to change. Pick a category your book holds, a window a live season covers, or a budget that the categories the scope touches can fund. The dry run runs again by itself whenever the declaration changes, and a compiled answer opens the buttons. Nothing was written on the refused one.
Where selling-date review applies, the Review step also compares the range with the commitment's dates and asks you to review a mismatch before you declare:
Review selling dates before confirming.
A product whose dates have no overlap with the commitment, or are invalid, keeps confirmation closed, and so does a check that did not finish ("Dates could not be checked"). If the dates change before you save, the page reads them again and asks for another review; it does not retry the declaration by itself.
Who to ask
Ask Tightly on Declare answers from this article, and Preview what signing arms runs the same compiler from a chat for a declaration already on the book. It writes nothing either.