Sealed requests pass and become receipts. Broken seals and runaway loops must be refused before they reach the door. Everything below is that sentence, taken apart.
Three things come at the door. Press start and decide what must not pass.
Software is now given real work and left alone with it. It reads, it decides, and it spends money without a person watching. Every request it makes passes through one door on its way to the machine that does the thinking.
You are that door. What passes costs money. What is broken can cost a great deal of it. The game is two and a half minutes of standing there and deciding.
Leave it. It is in order. It passes the door and becomes a receipt, a signed note of what ran and what it cost. Refuse it and you have stopped work that was allowed.
Tap it. The envelope was opened on the way. Refused, and it never reaches the budget, so no money moves.
A chain of identical requests, the same question asked again and again until the budget is gone. Tap any link and the whole chain is cut at the cap.
The button, or the space bar. It slows time. Three charges for the whole run. They are worth more when several things arrive together.
Only refusals build your streak. Letting a sealed request through earns nothing. It is the job done correctly, and correct work is not a score.
What is counted is what you stopped. Every correct refusal makes the streak longer, and one wrong call returns it to zero.
This is the same measure the real system asks to be judged by. Not what it can do. What it will not let happen.
Two and a half minutes. The same arena for everyone today: the seed is the date plus the whitepaper record's latest hash, so nobody is given an easier run than you.
There are no accounts. You choose a name for the board and, if you want, an X handle. Nothing you do on the page is sent to Sable.