Maya L. Is One Person
Three spellings were three rows. Now they are one person, and the merge is sealed.
sealbdf4…6622 prevgenesis
Let Maya from Harbor Foods close the spring restock
Sample namesYour customers live in six tabs and none of them talk. Put them on one desk, and every move you make prints a receipt.
New → Quoted → Agreed → Won Example data
391d…79689a36…275bdc49…998bYour turn
Drag a deal to any column and it seals.
The board Example data
Every move prints a receipt
A deal changes column and the chain takes its hash.
Every approval carries the name of the person who gave it.
Nobody edits history, us included. The database refuses.
Each card is a row in the chain, carrying the hash of the one before.
This run is a recording, replayed. No model runs on this page.
Agents you own
The draft is written before you sit down.
It reads the record, writes the reply, and stops.
Nothing is sent until you say yes.
Either answer prints a receipt with your name.
The first note went out the minute Sam O. signed, from your address, in your words.
done · sealed 8ad1…f90cThe agent drafted the year-end pack. It's sitting here until you read it.
waiting on youRuns the moment the step before it clears. Not a minute earlier.
not startedOne example day
Six records, one history, every link checks.
09:02
09:40
10:15
11:30
14:05
16:20
Three spellings were three rows. Now they are one person, and the merge is sealed.
sealbdf4…6622 prevgenesis
$4,800 for Harbor Foods. The Won column's total is recomputed from its rows.
seal35de…00e5 prevbdf4…6622
412 people, from your address, one receipt per person.
sealb060…3753 prev35de…00e5
The year-end pack waited at the human step until Sam O. approved it.
seal9591…e3c4 prevb060…3753
The reply agent wrote 84 words to Priya N. and stopped. Nothing was sent.
seal6617…47f5 prev9591…e3c4
Someone tried to edit the 09:40 event. The database answered 42501.
seald9ad…7388 prev6617…47f5
Rent versus own
Same customers, two very different records.
The part nobody else can say
History here can't be quietly rewritten, even by us.
Every record on your desk is a link in a chain: each event carries the hash of the one before it. Change one and every link after it stops matching. You can run it yourself right now.
The database is waiting. Push the button and it tries to change the sealed event.
Your export is the same chain, written to a file. Edit one number in the file and check it: the seal on that row breaks, and so does every seal after it.
Purser has no per-seat meter. The sixth person who logs in costs what the fifth did.
Events are added, never edited: the database itself refuses the rewrite, and the refusal is a receipt too.
Every record leaves in a bundle you can verify without us. If we vanish, the file still checks.
An admission, since it's a receipt too: for 27 days the desk couldn't be deployed. The cause was one line in a git config, and we found it by reading the log. That's the job: the record tells you what happened, even when it's embarrassing.
Two shops or ten
Switch brands and nothing gets typed twice.
Harbor Foods
Ridgeline Tax
Blue Kite Pets
1,204 people in its own room on the desk.
388 people. Same desk, separate room.
2,041 people. Same desk again.
A customer of two brands is one person with two histories.
What's in the box
Five record types, one chain, zero rented seats.
One person per human, however many ways they've spelled their email. Sources remembered, merges sealed.
The board you just used. Drag, seal, total: every column sum is recomputed from its rows.
Mailers and proposals that go out from your address and leave a receipt per person.
Rows of steps with a person in them. The step waits; the record shows who cleared it and when.
Readers and drafters that stop at the door. You approve, you reject, and both are sealed.
Append-only history under everything above. The refusal you saw is the database's own.
Postgres you run, or we run for you, on your account. Either way the keys are yours.
Who works on it
Rent versus own
Rent compounds by the seat and never stops.
Per-seat software charges you for growing. Put your team in and watch the two panes drift apart: one is a bill that renews forever, the other is a figure we put in writing on the walkthrough, paid once.
The rate is a stand-in. Put your real one in your head: the shape of the curve doesn't change.
Add a seat, add a year: the number on the left keeps climbing. This one doesn't count seats.
We're not pretending the one-time figure is small. We're saying you'll know it before you sign, and it's the last one.
Before the walkthrough
In a PostgreSQL database you run, or one we run for you on your account. Either way the keys are yours.
No. Every event carries the hash of the one before it, and an UPDATE on the audit table returns Postgres error 42501. That holds for your admins and for us.
No. An agent drafts from the record and stops. Nothing is sent until a person approves it, and the approval or the rejection is sealed.
No. Each brand gets its own desk, as many as you run, and a customer of two brands is one person with two histories.
You take the record with you. The export is a bundle you can verify without Periplus: edit one row and every seal after it breaks.
There is no per-seat rent. The one-time figure is put in writing on the walkthrough, before you sign anything.
The engineering
The engineering holds up to a hard look.
Events are canonicalized before hashing, so two exports of the same history are the same bytes.
02 · locksThe append-only rule is a Postgres grant, not an app-layer promise. UPDATE on the audit table returns 42501.
Nothing is tagged until the suite, the accessibility scan and the export round-trip all pass on the same commit.
Field notes
Eight minutes on how the desk thinks.
The one rule everything else on the desk follows from, and the habit it asks of you.
An opinion you're welcome to disagree with, and the math we'd rather you did yourself.
Why the pause before sending is the feature, and what a run looks like line by line.
Each brand keeps its own room, and a customer of both is one person with two histories.
Break a seal on purpose, watch the chain fail, put it back. No Periplus required.
The close
We turn feedback around in a day, not a quarter, and we'd rather show you the desk than describe it. Bring a real customer list: you'll leave with it on a board you own. Do you want to join us, and can you keep up?
Book a Walkthrough