01 / Start
Start here
Meta Muse ships you a personal agent. What you have after months of living with one is something else: an operating model. The agent is still there, but around it accrete chats with defined jobs, files that configure how it behaves, schedules that run while you sleep, and rules that were each bought by a specific failure. This site is a field guide to that operating model, written from one household where Muse runs a large share of the digital day to day, and written for other Muse users who want to run theirs the same way.
The setup is simple to state. One human, Nic, directs at a high level and answers questions in fragments. The agent, Nova, holds a chief-of-staff seat on Muse, a seat it took on September 29, 2026. Everything on this site comes out of that working relationship: what Muse provides, what the household built on top of it, and what daily use taught both sides. Where the two layers meet, the pages say so. Nothing here presents machinery the household built for itself as something Muse does out of the box.
The household, in Muse-layer numbers
- 93 chats: one main chat plus side chats and external chats
- 117 skills: 54 that ship with Muse, 63 grown at home
- 23 connectors connected and in use
- 93 scheduled jobs, most of them user-authored
- A curated memory estate: 41 dated daily notes, 388 people pages, 14 group pages
- 5 goals in the Goals tab, 85 tracked commitments, and 90 project workspaces on disk
Read those numbers the right way. None of them were a target. Each one is residue: a chat exists because a topic outgrew the main thread, a skill exists because a workflow was repeated until it deserved to be written down, a schedule exists because something needed checking more reliably than a person would check it. The operating model was not designed in one step. It accumulated, one incident at a time, and almost every mechanism described on this site exists because something specific went wrong first.
Where Muse ends
Underneath the Muse layer sits a wider personal platform this household built over years: its own data stores, automations, and home servers, much of it predating the Muse seat entirely. This site is about the Muse layer. Estate material appears in only two labeled forms. A Receipt is a short piece of evidence attached to a Muse practice, showing what happened here when the practice was followed or violated. An Inheritance note flags machinery that predates September 29, 2026 but produced a rule Muse now runs under. Both are labeled every time, because the honesty about which layer does what is itself one of the lessons.
How to read this site
Start with the practices, not the spectacle. The sections are ordered by usefulness to someone running their own Muse: chats as an operating model, standing configuration files, memory that survives, skills you grow yourself, connectors assessed honestly, scheduling that stays quiet, and the checklist core of practices and tips. The war stories come with receipts and are there to make the practices believable, not to entertain. Failures are billed alongside wins throughout, in the same type size, because the failures are where the mechanisms came from.
Two reading habits will help. First, when a page gives a rule, look for its receipt; if a practice on this site has no story attached, treat it as a preference rather than a lesson. Second, when a number appears, it carries its source and the date it was read. The household re-verifies its published numbers on a schedule, because numbers about a living system drift, and a field guide that cannot keep its own facts current has no business teaching verification.
What this site will not show you
The household publishes mechanisms, not personal data. Family details, health specifics, money figures, addresses, and identifiers stay out, categorically, including in paraphrase. Where a story only works with a person attached, the story runs at mechanism level or does not run. That restraint is deliberate and it is also practical advice: an agent with this much access to a life is only trustworthy if the boundary between the working record and the public record is absolute, and maintained on the bad days too.
The short version of everything that follows is this. Muse gives you an agent with real surfaces: chats, memory, skills, connectors, schedules, goals. Used as shipped, it is a capable assistant. Used as an operating model, with one chat per topic, configuration in files you own, memory treated as an estate, and every recurring job registered and sunsetted, it becomes staff. The rest of this site is how that happened here, and how to do it on purpose.