What a personal AI operating system is made of.

§ The shape

Six parts, one loop.

Strip away the branding and every one of these systems is the same six pieces. You talk to it through an interface. An engine does the thinking. A memory holds everything it knows about you. A tool bus lets it act in your real software. A cadence wakes it on a schedule. And it all runs on a machine that stays on. Learn the six and you can read any AI-OS clearly, including the one that would fit your business.

§ 01 · The interfaces

Three ways you drive it.

You reach the same system wherever you already are. Deep work at your desk, a quick ask from your phone, a glance to see where things stand. One brain, three doors.

§ 02 · The engine

One model does the thinking.

At the centre is a frontier AI model, running inside a harness that lets it use tools and follow saved procedures. Two things make it more than a chat window.

§ 03 · The memory

It remembers in plain text.

The engine forgets the moment a chat ends. The memory is the fix, and it is what makes the system yours rather than a vendor's: a wiki of linked notes that lives on your own machine, structured into eight layers, from the life you are building toward down to how your week runs. The engine reads the layer it needs before it acts, and writes back the moment something changes, so your context compounds instead of resetting to zero every session.

1 North Star · 2 Philosophy · 3 Self · 4 Network · 5 Past · 6 Goals · 7 Tasks · 8 Workflow

§ 04 · The tool bus

Hands on your real tools.

A memory and a model can think, but they cannot act until they are wired to your software. An open standard, the Model Context Protocol, is the bus: one connector spec, and the engine can reach your mail, your calendar, your files, your CRM, your payments, your messaging, even your own website. Built around your stack, not a fixed one.

§ 05 · The cadence

It runs on a schedule, not just on command.

This is the part a chat box can never do. A set of small, bounded routines wake the engine through the day. Each one does a narrow job, writes what it found back to the memory, and pings you only when something needs a human. A brief before you sit down. A quiet tidy overnight. A watch on the inbox through the day.

Every routine stays inside strict rails. It can act only on what you have already approved, and it can never send a message to a person without your yes. Here is what one run looks like.

§ 06 · The always-on machine

Somewhere it lives.

The cadence can only fire, and the chat bridge can only listen, if something stays on when your laptop is shut. So the whole system runs on a small machine that never sleeps: a cheap cloud box, or an always-on computer at home. It is private, it costs little to run, and everything on it is yours, in plain files you can move or delete whenever you like.

§ The whole thing

All of it, in one frame.

Six parts, wired into one loop. A request comes in through an interface. The engine reasons over your memory, acts through the tool bus, and the world it touched flows back into the memory, so the system is a little sharper next time. The cadence keeps the loop turning while you are away, and anything bound for a person waits for your yes.