Personal operating layer

I built an orchestrator-and-sub-agents architecture to run the company. The obvious question is why it should stop at the company's edge. My own life has the same shape as the business. Recurring work, a knowledge layer that holds the why, and decisions that mostly just want the right context in front of me at the right moment.

How it works

The plan is that orchestrator idea turned inward. One chief-of-staff surface routing to scoped helpers over a personal knowledge base, exactly the way the business orchestrator routes to department sub-agents over the Obsidian vault. The business one is not a separate program. It is a configured Claude Code session with a routing brain and per-agent tool allow-lists as its security boundary. The personal layer would ride the same always-on Mac mini, the same phone-first pocket copilot bridging to headless Claude, and the same guardrails, with money and destructive actions gated. Systems of record hold the how much and the when. The knowledge base holds the why and the what.

Where it stands

Planned, and really the endpoint the rest of the personal seat is quietly building toward. Each Live personal system (the health dashboard, the net-worth view, the home-network monitor) is a probe confirming the business stack generalizes cleanly to one person's life.

If it works for the business, it works for me. The operating layer does not stop at the office.

This is where the company-of-one bet stops being about hotels. If one owner plus agents can hold an entire C-suite, the same pattern can hold a life. The marginal cost of adding me as a tenant is near zero, because the whole stack already exists. Growth by agents instead of headcount, all the way down.