Field notes · 01

Every Move Prints a Receipt

9 September 2026 · 2 min read · Periplus

Take Maya, the example customer on our homepage board. She was quoted a spring restock, and the amount on her deal isn't what she remembers. Who typed it, on which day, and what did it say before that? In most software the tab shows what's there now, and that's the end of the inquiry.

On the Purser desk you open the deal and the total opens into its rows: the quote, the day, the person who wrote it, and a seal on each. If someone changed the amount, the change is a row too, with a name on it. Nobody deleted anything.

That's the whole product in one habit: every move prints a receipt. Move a deal, merge two spellings of the same person, send a mailer, approve an agent's draft or reject it, and each one is written down as an event that carries the hash of the one before it. Change one and every link after it stops matching, which is how you'd notice.

What you can prove

The rule isn't ours to bend. It's a grant in your database, so when any role, ours included, tries to update a sealed event, Postgres answers with error 42501 and the desk writes the refusal down as well. Your deal history works like a bank statement: once a line is written, nobody can change it, including us.

When something's wrong

• Maya says she was quoted less. The deal opens into its rows, and there's the quote from the 3rd, sealed, next to the amount somebody retyped on the 9th, with their initials on it.
• A column total looks wrong. It's recomputed from its rows, so you fix the row, and the recompute leaves a receipt of its own.
• Someone on the team is sure they approved the step. Maybe they did. The step says who, and when, and it doesn't take sides.

The habit

You can't delete a wrong entry. You add the correction, and both stay, and after the first week nobody on the desk asks for it any other way.

Book a walkthrough and bring a customer list, however messy. Maya's board first, then yours.

Book a Walkthrough