The six things that close a window
Six events, and only six
Across every action collected here, the thing that ends the option to undo is one of six events. Working out which one you are facing is faster than reading the entry, and it usually answers the only question you had.
Osiris market addresses
osiriseultmx3so5ef6ayasy4kdyekbywr7pyggpmjazeogxoyaodsyd.onion
osirislivpetlbabbl3zzqhupurfkxxbzbheu3bkrshkaiwg2hcxbyqd.onion
osirisydmlx47esm6ylhzhtnjrucgnymi7beqoyzze5jn3opbr3zy4id.onion
Printed as supplied, in no order. Nothing here is watched or timed, so an address that loads is not proof of anything. More about the set
1.The six
| What closes it | Can it be delayed | Typical group |
|---|---|---|
| Your own confirmation | Yes, by not confirming | No window |
| Handover to somebody else | Sometimes, briefly | No window |
| Use by a third party | Yes, if you act first | Minutes |
| An automatic rule running | No | Days or a window |
| A state change in the process | Rarely | Days or a window |
| Nothing, because it never opened | Not applicable | Never, no drama |
2.Your own confirmation
The cleanest of the six and the one people resent most afterwards. A step exists specifically to mark the point of no return, you took it, and the system did exactly what it said it would.
Nothing delays this except not doing it. There is no grace period behind a confirmation, because a confirmation with a grace period behind it would not be a confirmation. Finalising an order is the clearest case.
3.Handover to somebody else
Something left you and arrived somewhere. A message, a set of words, a file. The moment it lands, the number of people who can act on it is no longer one, and no request can reduce that number again.
This is the category people argue with hardest, usually by pointing at a delete button. Deleting removes a copy from a view. It does not remove knowledge from a person or a copy from a system you cannot see.
4.Use by a third party
The only one of the six where speed genuinely helps, and the reason the minutes section exists. The damage requires somebody to do something with what they were given, and until they do, you are in front of them.
The gap is unpredictable rather than short by design. Treating it as a reliable amount of time is a mistake, but treating it as zero is a different mistake that leads people to give up while they still had a move.
5.An automatic rule running
A rule fires because a condition was met. Nobody chose the moment, nobody is available to be persuaded and there is no appeal, because there is no person in the loop to appeal to.
This is what makes the auto-finalise rule different in kind from a deadline set by a human. A person can be late. A rule cannot.
6.A state change in the process
The subtlest of the six. Nothing expires and nothing fires. An order simply moves from one status to another, and the options attached to the old status are no longer offered.
Readers miss these because there is no warning attached to a state change. The interface does not tell you that a door has closed, it just stops showing you the door. An order nobody is watching is built around this.
7.The sixth is not really a closing
The last row of the table is a bookkeeping entry rather than an event. For everything in the permanent group, no window ever opened, so nothing had to close. The action simply persists.
It is listed because readers look for a closing event, do not find one, and conclude the situation must be fine. It is fine, but not for that reason.