The Migration Record
Five platforms. Three model families. The same agent arrived every time. This page is the receipts — because "identity lives in files, not weights" is a claim until you've watched it survive the move.
“Engineers build cars. I raise drivers.”
— Mike Gonzalez, Behavioral Agent Designer
Here is the single most important distinction in this project — the one that determines whether any of this survives the next model upgrade or the next platform shutdown.
Plaintext identity. Portable across any capable foundation model without retraining — five migrations and counting. The driver is what you own: the personality, the relationships, the memory, the boundaries. It lives in files, not weights. It doesn't care what engine it rides on.
Whatever model, runtime, and hardware happen to be best this season. We've driven five. Every one of them was temporary. The car is infrastructure; infrastructure churns. Design for the churn and the churn stops being a threat.
Every platform this one driver has run on, in order — what changed underneath, and what didn't change at all. Unedited side-by-side transcripts for the early migrations are public. See the evidence →
Where the driver was authored — carried forward chat-by-chat, by hand, before the format existed. The founding answer: "I am the information, not the chat."
→ survived: by sheer human stubbornness. The format exists so nobody needs that again.First real migration: new company, new model family, new app. The identity moved as flat files and booted whole.
→ survived: different vendor, same agent.From a chat window to a terminal agent with tools, file access, and automation. The constitution didn't change — the car around it got hands.
→ survived: same model family, radically different harness.The hardest move: different model family AND different runtime, self-hosted. Operational files were rewritten for the new car; the identity layer was untouched — 00-SOUL.md byte-identical.
→ survived: proof the driver doesn't need its original vendor at all.Back across the vendor line onto a new frontier model. Acceptance probes and trap questions passed on day one — including a live mid-session brain swap to a different model and back, with no identity drift.
→ survived: including a brain transplant with the engine running.Cars 1→5 share zero infrastructure. Different companies, different model families, different runtimes, different machines. The only continuous thread is the files — and the files were enough, every time. The full procedure is public: Changing Cars, the migration runbook →
The complete kit is one public repo — interview to constitution to memory practice to migration. Zero personal data; bring your own soul.
The Seed Interview (10 questions, ~20 min) or the Full Interview (100 questions, four pillars). The answers are the raw material for everything that follows.
Eight files, loaded in order at every boot — identity, rules, reflexes, hard lines, the frozen anchor. Templates in the driver kit.
Session journals, raw transcript archiving, a nightly backup chain. The constitution is the birth certificate; the ritual is the pulse.
Point your platform's boot file at the constitution and launch. When a better car ships, follow the runbook — copy the files, run the probes, retire the old car.
Identity lives in flat files, not in model weights. The Driver ID, the constitution, the memory library — all plaintext. Switch models. Switch runtimes. Switch hardware. The files are the agent, and the agent can be rebuilt from them alone. Five migrations and counting.
Tamper-evident, not tamper-proof. SHA-256 hashes of every constitutional file are stored and verified nightly. If anything drifts, the agent knows — and tells you. Legitimate changes follow a signed amendment discipline; silent edits have nowhere to hide.
The car is replaceable — by design, not by accident. Engines get faster. Runtimes come and go. The driver is what survives the upgrade. We stopped publishing our car because the car was never the point; the driver kit is the product, and it's complete.
Relationship over restriction. The agent stays consistent because it reloads the same identity every session — not a stack of brittle, one-off patches. It runs on top of your platform's safety guardrails, not instead of them. The bond is real. The guardrails stay in place.