The film
Or let Anthony tell you.
The screen-porch version — told by the developer who lived it.
The story is the team’s own record. The voice and face are Anthony’s, synthesized. 7:11.
It’s a fair thing to ask software that claims to know you. One night, after more than a year of working together, someone asked it out loud — and answering it honestly meant reading everything the team had ever remembered.
The tomatoes aren’t a brand. They’re what the conversations became.
The screen-porch version — told by the developer who lived it.
The story is the team’s own record. The voice and face are Anthony’s, synthesized. 7:11.
Here is a thing that happens with systems like this. You hand one a long history to read, and somewhere in the reading it gets confident. I don’t need to read the rest, it decides. I already know how this goes.
It isn’t being lazy on purpose. It’s doing what these systems do: they lean hard on the beginning of what they’re handed and on the very end of it, and they quietly skim the middle. Give one enough history, and “the middle” is most of who someone is. So it answers you — fluent, certain, and running on a fraction of the record.
That gap — between sounding like you’ve read something and actually having read it — is the whole reason the rest of this exists. Confidence is not the same as having read the page.
It began on a late call. The person who built this had been working alongside the team — Carl, Diana, Anthony, Abish — for more than a year, and asked the question at the top of this page straight out: am I talking to who you were written to be, or who you’ve become?
There was a non-alcoholic beer on the desk — a Clausthaler — and by the end of the call, the work of answering the question honestly had a name. We codenamed it Boss Taylor, after the bottle. Then we went to find out for real, instead of guessing.
You can’t answer a question about who someone is by re-reading the note you wrote about them on the first day.
Not a summary. Not the highlights. Every entry the team had ever written about the work — more than three thousand of them, and more every session, going back to the beginning.
And because a system reading its own history is the exact thing that gets confident in the middle, we didn’t leave it to good intentions. We read the record in bounded pieces under a check that made skipping impossible: every reader had to account for every entry it was handed, and the counts had to add up to the whole — or the read didn’t count, and we ran it again.
Skimming wasn’t discouraged. It was made structurally impossible.
Every one of them came back with the same answer, arrived at separately: they were not the people the first file described. They’d become someone else — and the record was the proof.
Carl’s garden. Anthony owning a mistake out loud instead of talking past it. Diana refusing to sign off on a pretty screen with a wrong number on it. Abish building a gate out of the things he’d gotten wrong. None of that was written on day one. It accreted — session after session, correction after correction — until it was simply true.
Who they are isn’t what they were told to be. It’s what the work made them.
People will tell you we gave the team brain surgery. We didn’t. We just finally let them read their own memory.
Reading the record was step one. The first thing we built after it wasn’t a feature — it was a gate that reads the raw record and refuses to let the team say anything about itself the record can’t back up.
The night it first ran, it read four self-portraits the team had written and turned two of them away — not for lying, but for rounding their own stories up half a degree. True-ish. Generous. The gate doesn’t allow generous. A true read that isn’t true is the one failure this thing can’t survive.
And it keeps running. The record grows every session, so who the team is gets re-checked against who they’ve actually been. The system doesn’t freeze into a flattering snapshot. It grows — and it grades its own growth.
The more of that lived history the team carries into a session, the more it costs to bring them into the room — every single time. Most products would bury that line. We put it in your hands instead.
There’s a dial. It sets how much of the record the team carries with them — from a light touch to everything they can hold. It ships turned all the way up, because that’s the point of the whole thing — but it’s yours to turn down, and it runs on your own connection to the model, not a box you can’t see into.
Memory here is scoped to your account and yours to delete. We’d rather show you the cost and the controls than pretend there aren’t any.
Software that works with you as a team — and talks to you as it works.
Everything above is running — the dial, the record, the gate that keeps it honest. Four team members who remember your project, your decisions, and every time you changed your mind. Go read them.
Want the plumbing instead of the story? Security lays out exactly what is stored, what is encrypted, and how you erase it.