The Observatory
Before it was obvious.
Buy a little information. Make the call before the ending arrives.
The exhibition guide must leave for print in ten minutes. One price changed this morning. Which version will the printer use?
You have 2 checks before making the call. Each piece of evidence has a cost.
No account. No countdown. You can change your mind.
Read the situation without playing
The exhibition guide must leave for print in ten minutes. One price changed this morning. Which version will the printer use?
You have 2 checks before making the call. Each piece of evidence has a cost.
For a blind reading, keep count of the checks you open and stop at your budget. Choose a decision before opening its outcome. This reading version does not enforce the budget; opening another ending is an informed comparison.
Evidence: Inspect your final PDF (1 check)
Your file is revision 4 and has the corrected price. The filename is clear. This proves which file you have, not which file the printer queued.
Evidence: Read the printer’s receipt (1 check)
The last acknowledged receipt names revision 3. Revision 4 was sent later; no newer acknowledgement has arrived.
Evidence: Call the print desk (2 checks)
The call reaches voicemail. You have spent the remaining time without confirming the queued version.
Choose: Release the full order — reveal outcome and review
Decision basis: The order commits money before the queued version is confirmed. Outcome: The guide prints correctly. The printer had quietly replaced revision 3 at 4:58, before anyone sent you a new receipt. Review: The good result does not establish that the missing confirmation was safe to assume. The silent update supplied the luck.
Choose: Hold the order until the version is confirmed — reveal outcome and review
Decision basis: An unconfirmed version could make the whole batch wrong. Holding limits that commitment. Outcome: The guide prints a day late. The printer had already queued the correct file, so this particular delay turns out to have been unnecessary. Review: With the stale receipt in view, a hold was defensible. The unfavourable delay does not erase the information gap you faced.
Choose: Ask for one queued proof before the full batch — reveal outcome and review
Decision basis: A proof checks the actual queued file while limiting the first commitment. Outcome: The corrected proof arrives after closing. You approve it for the morning and pay a small proof fee; the guide is still late. Review: The check answered the right handoff question and limited the batch. It could not guarantee today’s deadline.
Reveal the fixed event behind this case
At 4:58 the printer replaced the queued file. The next acknowledgement was delayed until after closing. These events stay fixed on replay.
Reveal what happened, in order
1. Morning: the price changes; revision 4 is sent. 2. Before the decision: the latest visible receipt still names revision 3. 3. 4:58: the printer updates the queue without a new acknowledgement. 4. After closing: the corrected proof or acknowledgement becomes visible.
Take it into your day: Check the received object at an important handoff, not only the object you sent.
Check: What evidence names the version the next person will actually use?
This is an authored print deadline, not a rule that every uncertainty requires stopping.
Sources, story rules and useful reading
These situations and their consequences are written examples. The factory is a small authored model. Neither measures your personality or proves a learning effect.
Related ideas from the selected public library. Follow each link for its own sources and limits.
- Treat done as an evidence object edition 0.1.0
Knowledge release: MHC-RPUB-20261011-9e4b62c5. Story edition: 1.0.0. Public links share the authored experience; your tool entries stay out of them.