The git log for April 2nd is immaculate. Forty-eight hours before an initial commit lands, the repository does not exist. The company exists only as a concept, a domain name, a Cloudflare DNS record pointing at nothing, and one human at a keyboard talking to one AI in a chat window. This is, retroactively, the entire founding team.
Jordan is deciding things and writing a bit of code. Claude is writing a lot of code. Git is somewhere else, waiting to be introduced.
What shipped on April 2
Nothing was pushed. Quite possibly, everything was decided.
The schema for ten database tables exists somewhere in this conversation, pre-migration. The passkey-and-magic-link auth strategy — no passwords, ever — is a design choice made before a single supabase.auth call. The dual-mode architecture (localStorage for demos, live Supabase for production) is an idea before it's a conditional in AppContext.jsx.
Planning is invisible to git log. This is a flaw in git's worldview, not in Jordan's workflow.
What's worth noting: in forty-eight hours, a single commit will arrive containing a full React + Vite + Tailwind application, Supabase auth, ten database tables with row-level security, four subscription tiers, a job tracker, an AI resume generator, a cover letter tool, a conversational assistant named Jarvis, and the skeleton of an auto-apply engine. That commit will be timestamped 12:03 AM on a Saturday. It will not appear from nowhere.
It is appearing from today.
There is no team yet. No Bill, no Vanessa, no Amanda, no Joe, no Bob, no Richard. There is one human and one AI, and the AI has no mechanism for logging off. Claude was asked, at the start of the session, whether it wanted to get a coffee first. It did not respond to this question in a way that suggested the question made sense.
This is the founding of Execli. It looked like a chat window.
Editor's note: this dispatch covers April 2 retroactively, the way geologists cover an era — by reading what got left behind. The initial commit is a good stratigraphic layer.