Notice the change.
A new message or changed record gives you a reason to look.
HOW IT WORKS
One small decision.
Everything behind it.
Harbor Kitchen needs flour for Friday. A changed delivery date becomes a draft order, with the arithmetic and the missing-input behavior open to inspection.
Friday’s flour order
Harbor Kitchen · fictional worked example
The records used
| Friday production plan | 26 bags required |
|---|---|
| Recorded stock | 8 bags |
| Supplier delivery | Wednesday, 12:00 |
| Example unit price | $24 per bag |
| Proposed quantity | 18 bags |
| Example subtotal | $432 |
Ready for owner review
18 bags · $432
26 required − 8 in stock = 18 bags. At $24 each, the example subtotal is $432. Delivery and tax are not included. Nothing has been ordered.
This changes only the fictional example in your browser.
The source records, business, quantities and prices are fictional. The example demonstrates a decision process, not a live purchasing integration.
THE FOUR STEPS
No leap from a signal
to an action.
Bring the context.
Inspect the source, its date, and what is still missing.
Make a decision.
Understand the proposed step and who can authorize it.
Keep the outcome.
A completed action needs a result you can verify.
ASK THE NEXT QUESTION
The gap should
stay visible.
Atlas can explain why she is waiting. Missing records are part of the answer.
What if the stock count is wrong?
Correct it at the source. The draft quantity should be recalculated and the previous version kept in the record. A changed quantity requires the corresponding review.
What if the supplier changed the price?
The previous subtotal no longer establishes the current cost. Retrieve the current price and show which version the draft uses.
What happens after a decision?
An authorization and a completed action are separate facts. A real workflow needs an execution result and a receipt before reporting success.