The Booth
The surface I run my week from
Six lanes of work—a job search, this website, an editorial calendar, a newsletter build, operations, and a personal list—merged into one day and ranked against a time budget. Every decision made on it is written back into whatever system owns the record, and tells you where it landed.
It is the tool I actually work out of, built in Claude Code over a few months of using it. The demo behind this page is the real surface running on a recorded day with an invented corpus—not a mockup, and not a video.
Have a login?
Sign in with the username and password I sent you.
The demo
What you are looking at
Every person, company, role, message, and post in the demo is invented. The corpus is generated from the schema rather than scrubbed out of mine, and that was a measurement rather than a preference: across my real contacts, 99% are identified by their job title and employer alone, and 71% are the only person on file at their employer. Renaming the row changes nothing—“Senior Engineering Manager, Games at <employer>” is a search that returns one human. A structure-preserving scrub produces pseudonymized data, and pseudonymized data is still personal data precisely because it can be re-identified. Generating from schema removes the question: there is nothing to verify, because nothing was read.
The clock is frozen at one date so the day does not slide into an empty week. Two things stay live rather than recorded: decide a card and the day re-plans itself against the minutes that just came back, and a note typed into a network card is genuinely read for what it says about the relationship. The rest is a recording of the real surface answering its own requests.
The surfaces
Four views over one set of records
Not four tools. One day, one week, one career file, and one map, all reading the same records—which is why a decision taken on any of them means the same thing on the others.
Today
The merged day, and the only view that answers what to do now.
Every lane’s work is interleaved so no day is all one kind, each card carries the lane it came from, and the whole day is sized against a time budget rather than a list. Meetings come off the top as fixed points; habits sit outside the budget until one is genuinely late.
The week
Where everything sits, which is a different question from what is next.
Recurring work is stored as rules and expanded on read, never written into days—so extending the schedule is not a migration, and a habit skipped on Tuesday is skipped on Tuesday only.
The career file
Roles, rounds, contacts, and the routes into a company.
It reads the mailbox. A rejection closes a role, a reply closes the card that asked for it and records everyone who was on the thread, and a ranked list of who might introduce you is built out of what the file already knows rather than out of a connection degree.
The map
Every open initiative across every project, in one dependency graph.
Rows are lanes and columns are depth, so the first column is everything that can be started today. It is the planning surface the other three draw work from.
The design
Three rules the whole thing obeys
The interesting part of this project is not the views. It is the constraints underneath them, which is also the part that transfers to a team.
A decision is written once, and says where it landed
Every card is a projection of some other system’s record, so “done” has nowhere to live on the card itself. One write path takes a decision and propagates it into the system that owns it—and returns a receipt naming every file it wrote and every system it skipped, with the reason. Some decisions genuinely cannot propagate. Those say so rather than diverging quietly.
Automation writes to the record, and shows its work
The mail lane closes roles and creates contacts without being asked. Every automated write logs the value it replaced, the words it was read out of, and which run made it, with an undo on the record it touched—because the risk that matters is not who wrote the change, it is whether the change can be taken back.
Anything that can reach the internet cannot reach the data
Two of the jobs behind these surfaces hold a web search. Both are denied the state folder outright, and what they legitimately need is projected into a separate directory whose one rule is that everything in it is safe to read beside the internet. The deny is a blanket with no hole cut in it, because a hole is where the next sensitive file quietly becomes readable.
Next
Two things you might want
A look inside
Logins are issued one at a time, so the demo stays something I show people deliberately rather than a link that ends up indexed. Email me and I will send a username and a password, usually the same day.
Something like it, for your team
The Booth is what my consulting work looks like when the client is me: lifecycle and data infrastructure, built to be operated rather than admired. Rates and scoped engagements are on the consulting page, and a 30-minute call is the fastest way to find out whether this is the shape of the problem you have.
More on how I work: case studies, résumé, and LinkedIn (opens in new tab).