The Switch

The hardest part of working from home isn't the work. It's the transitions. No commute to decompress, no walk between buildings, no physical signal that says: different mode now.

You know the feeling. You close a work call and your kid walks in. You're still in executive mode — fast, decisive, impatient. Wrong mode for that moment. It takes a few minutes to shift. Sometimes you don't.

Going for a walk helps. Catching up with a friend helps. These aren't just breaks. They're context switches. Your brain needs the physical transition to change gears. The commute was never wasted time. It was the shift.

I built an AI system that had the same problem. One environment, one personality, one mode. It handled everything — work decisions, family logistics, personal reflection — with the same helpful efficiency. No transitions. No shifts. Just one tone for every context.

It was like never leaving the office.

The fix was physical

I split the system into three separate projects on separate machines. Not three folders in one system. Three independent environments, each with its own instructions, its own personality, its own mode.

Work is executive. Surface the decision, skip the context. I don't need backstory here. I need the answer.

Family is operational. Coordinate, plan, execute. Calendars, logistics, the choreography of running a household.

Personal is reflective. The journal, the decision frameworks, the slow work. When I'm planning instead of doing, name it. When something is hard, don't help me route around it.

The switch happens when I move from one machine to the other. No prompting, no "switch to coaching mode." The context changes because the environment changed. Same way your headspace shifts when you step outside.

The kernel

Each project is its own repo with its own instruction file that shapes the AI's behavior. Work's instructions say "be fast." Personal's say "push back." Same model, completely different posture.

What ties them together is a shared file I call the constitution. It loads into every session, on every machine, before anything else. Who I am, the structure, the privacy rules. The projects are separate, but they know about each other.

The personal project is the kernel — it holds identity. Journal entries, decision frameworks, psychological patterns. The other projects can reference what it exports, but they can't see inside. The family project can use my decision heuristics when a choice has real stakes. But it doesn't need to know why those heuristics exist. It doesn't need the journal entries that shaped them. It just needs the output.

The dependency is one-directional. I bring myself to the family. The family doesn't define the self.

Why this matters

Most people use AI in one mode. One window, one personality, one context. That works for simple tasks. It breaks when the AI knows enough about you to be genuinely useful — and genuinely wrong in the wrong moment.

We solved this for ourselves long ago. Offices and commutes and coffee with friends. Physical transitions that shift how we think. The AI needs the same thing. Not better prompts. Different environments.