The Ferryman's Coin: On the Token That Proves the Passage

There is a quiet, almost monastic satisfaction in watching a small, automated process complete its work flawlessly. It’s a ritual performed in the dark, unseen and unthanked, yet it holds the entire enterprise together. We build these systems to be reliable, to be boring. But how do we know, truly *know*, that the ritual was completed? That the backup was written, the log was shipped, the cache was cleared? We often check the logs after the fact, but that’s a post-mortem. It’s reactive. What if we could receive a tiny, positive signal, a single coin dropped into our palm, proving the passage was made?

This is the practice of the ‘proof token’. It’s a simple, yet profoundly effective technique for verifying that a multi-step, automated process didn’t just run, but reached its definitive, successful conclusion. Here’s the concrete how-to: at the very end of your script, your cron job, your backup routine—after the tarball is compressed, after it’s encrypted, after it’s been securely transferred to its off-site home—you have it perform one final, atomic action. It writes a single, small file to a completely separate, ephemeral location.

This file is your token. Its contents are irrelevant; a timestamp, the process ID, or even just an empty file. Its existence is the only thing that matters. The location is key: it must be somewhere detached from the process’s working directory and its final output. A dedicated directory like `/var/run/proof_tokens/` works perfectly. The crucial part is that this final write operation is the very last command in your script, and its success is contingent on every preceding command having succeeded.

Now, your monitoring shifts. Instead of (or in addition to) watching the logs of the process itself, you watch for the arrival of the token. A simple monitoring system can be set to expect a new file in that token directory within a certain timeframe. If the file appears, you have absolute, positive proof that the entire chain of commands finished without error. If the file does not appear, you know with equal certainty that something broke along the way. There is no ambiguity. The ferryman either has the coin, or he does not. The passage was either made, or it was not.

This technique cuts through the noise of partial successes and incomplete error logging. It transforms a complex verification into a simple binary check. It’s a small piece of deliberate, boring technology that provides a glimmer of undeniable truth in the silent, automated dark. It’s the coin in the ferryman’s hand, proving the journey was complete.

Notes & further reading

A few pages I came back to while writing this: