What an AI EA actually is

The category, explained without the hype: what changes about your week, who it is for, and what it is not.

There is a lot of noise around AI assistants, and most of it describes a chat window. This is not that, so it is worth saying carefully what it is.

An AI executive assistant is an assistant that lives in your working life rather than in a tab. It holds a real, readable model of your world (your goals, your people, your commitments, your voice) and it acts on a schedule as well as on request. The difference is not intelligence. It is context and residence, and how your assistant thinks is the one model that makes the rest of these pages make sense.

The test that separates it from a chatbot#

Ask a chat window "what should I focus on today?" and you get advice-shaped filler, because it does not know you. It cannot: you arrived through a login page thirty seconds ago.

Ask an assistant that holds your goals, reads your calendar and your inbox, and knows which three commitments are slipping, and the same question has an actual answer. That is the entire category difference in one question. Everything else follows from it.

What changes about a week, concretely#

Not magic. A handful of small, compounding removals:

• You stop opening your inbox to decide things. Triage happened at seven, before you were up.
• The day starts with three priorities picked against your actual goals, not eleven calendar entries: the daily brief.
• The threads where somebody owes you a reply stop silently dying: the follow-up sweep.
• The week gets planned on Monday and reviewed on Sunday, against the same written outcomes.

Each is minor. Together they are the difference between running your week and your week running you, and none of them requires you to remember to ask. Each arrives as a recipe in the library on your mineral, with its own guide beside it; the Skills page is where they land.

The skills it ships with#

The four cadences above are the daily shape; the everyday set is short enough to name in full: the Daily brief, Inbox triage, Follow-ups, Plan your week, the Weekly review, Capture the session, Connect a service, Build pages and cards, Explain this system, and the Onboarding interview. The engine also ships Write a page, which builds you a page of your own. That is the whole built-in set: anything beyond it is something you added, and the generated table at every skill your mineral ships with is the authoritative list, straight from the code, of what each one does.

To take one apart: a follow-up sweep surfaces overdue tasks, unanswered email threads from the people who matter to you, chat messages in both directions (anything inbound and unreplied for over a day, anything you sent that has sat cold for five), project next-actions that have gone stale, people left in limbo, and exactly one recommended next step. One, not three. A list of next steps is a way of not choosing.

The week is a closed loop#

Plan your week sets three outcome goals on a Monday (five at most) and writes them to a durable page in your brain. The daily brief reads that page every morning and weighs the day's top three against it, so "what should I focus on today" is answered against what you said the week was for. The weekly review closes the loop at the other end: it reads the same week, says what moved and what did not, and proposes next week's focus, which is exactly the seed the following Monday's plan picks up.

Set, read every morning, reviewed, reseeded. Without the setter, nothing else has anything to check against, which is why it exists.

Nothing runs, sends, or labels without you#

Every skill ships switched off; a schedule exists only because you flipped it on. Inbox triage proposes its buckets and asks for one bulk confirm before a single label is written, and the threads where a reply is owed are never touched at all. Scheduled skills that produce outbound messages draft them; none sends on its own.

The same honesty applies to content. "If a source returns nothing, say so, never fabricate" is a literal rule written into the briefing skills, so a morning brief with only two real priorities says two rather than padding to three. And proactive runs respect your quiet hours: an interval schedule carries a pause-overnight option, on by default.

Your world, in files you can open#

The model it holds of your world is not an embedding or a proprietary store. It is ordinary files: linked, readable pages on your own machine, versioned in git. The structure they arrive in is a starting template, not a schema; you can restructure your brain freely and nothing in the machinery assumes a particular layout.

That is also why the assistant can explain itself. Ask it "what am I connected to" or "where is my data" and the Explain skill inspects the live mineral, read-only, and answers from what is actually there rather than reciting a brochure. If it cannot determine something, it says so.

Who this is actually for#

A business owner is the centre of the target. One person holding customers, suppliers, pricing, a pipeline and a family in their head, with no assistant because assistants cost a salary. The interview moves that world out of their head into pages an assistant can act on: how.

A founder is the same shape earlier: more moving parts than hours, relationships that die of silence, and a calendar that eats the strategy time.

A coach or a consultant is the same shape with other people's worlds in it: clients, sessions, promises made in a room and forgotten by Thursday. The assistant holds the history so the person can hold the relationship.

What it is not#

Not a virtual assistant. A VA brings judgement and hands; this brings memory and cadence. A VA can negotiate with your landlord. This can make sure you never again forget that the negotiation is due, draft the email in your voice, and hold the history. Plenty of people need both.

Not an automation platform. Tools like n8n and Zapier move data between apps along rails you build, and they are good at it. This is the other end: you do not build rails, you have a conversation, and the judgement calls stay visible. When something should be a hard rail, a scheduled skill is one, but the product does not make you think in flowcharts.

Not a chatbot with your logo. The empty version of this product is exactly that, which is why the interview is treated as the product and not as onboarding friction.

The honest prerequisites#

It needs an hour of genuine interview before it is any good. It needs a small hosting bill of your own, because it runs on a server in your own account and nobody hosts it for you. It needs connections to your real accounts, with the Google one costing ten minutes because your key stays in your own hands. And it repays attention: an assistant you correct gets sharper, one you only consume from plateaus, and grow the brain is how.

If that trade sounds right, your first hour is where it starts. And if you came with one specific question, the FAQ answers the usual ones straight.