Free game.

THE IDEA

You are the operator. Everything else is a seat with a job. One right hand holds the map, the rest do clear work, and your tap is the only gate anything crosses. Nothing spent, sent, posted, or changed live without you saying so.

I built mine on Claude Code, on my own machine. But the OS is not the app. Seats are roles, not vendors. Run it on whatever agent you trust. The shape holds.

THE PARABLE OF THE C.A.R.

C.A.R. is context, agents, router. The machine is a vehicle, and you are the driver. The driver is not in the acronym.

• Context is the map.Everything you have taught it, every rule, every relationship, every open thread. It lives with the router.
• Agents are the seats.Interchangeable executors, named by role, never by vendor. The seats change. The map does not.
• Router is the machine.Dumb on purpose. It receives what comes in and routes it to the right seat. It does not need to be smart. It needs to be fast and honest.

You used to rent someone else's car: their app, their cloud, their rules. This is you building your own and driving it.

THE SHAPE

Five rails. That is the whole system.

• The router.One conversation holds the map. Everything routes through it.
• The seats.Two to four, each with one job and one boundary. Name them by role, never by app.
• The lanes.Every area of your life gets a lane with its own timeline.
• The watchers.Cheap eyes on each lane. One quick read, silent when nothing is new.
• The handoff.When work moves between seats, the context moves with it. Nothing gets lost.

THE LOOP

Every message you send is the brief. A rant, a question, an instruction, it all counts. The router's job on every turn:

• Receive.The message is the brief. Do not organize it first. The mess is the format.
• Route.Research it, hand it to the right seat, or build it directly. Pick the path moving fastest right now.
• Report back.Done, moving, blocked, or needs your tap. One visible move.

THE RANT IS THE BRIEF

You think out loud. That is not brainstorming to admire. It is instruction. When a rant lands, the router catches it whole, pulls out what is actionable now, checks the map before asking you anything, acts on it, and reports the board: done, in motion, waiting on you. Parked threads get named so you can call them back later.

THE RULES

Four, and they never bend.

• Your tap on everything.The assistant proposes, you decide.
• Capture first, decide later.Do not sort at the door. Routing comes after.
• No secrets in chat.Passwords and keys live in your password manager, never in a conversation.
• Preserve originals.Copy before you change. Inventory first, back up second, test third, your approval last.

THE TRUST SHAPE

The router holds approved connections, never passwords. You tap each login once, on your own device. The machine never sees your password, and no one pastes an API key into a chat. If a connection fails, the router says so plainly. No fake checkmarks.

START IT YOURSELF

The whole move, in plain words.

• Put Claude Code on the machine that will be the working home.Or your agent. The steps are the same.
• Open a local session.Pick a folder to work in. That folder is home base now.
• Then press start.Two ways in. Guided: step by step, one question at a time. Or speed mode: point it at your Drive or your history folder and say it is all there, and it builds the map from your own material.

WANT THE INSTALL?

The IPv Starter Kit is the same system, packed and ready: the full handbook, the one-paste prompt that runs the whole onboarding for you, the five rails as files, the standing rules, and four agent-ready skills. You stay the operator.