RimaruBook a call

Maru

Here's the company brain I built, how I got there, and where it stands.

The problem

Every new AI chat shouldn't need a fresh explanation of my company, my projects and what it's allowed to do. And I was explaining it every single day. Facts went stale, the same thing lived in different places, and files sat on one computer and not the other. What I wanted was one brain for the company: one place where everything lives, always up to date, that every AI and every person reads first.

Maru as an always-on assistant: a dial labelled Maru holding context, permissions, decisions and unfinished work, directing Claude and Codex, with a live feed: morning brief ready, 2 decisions need you, handover sent to Codex.

The Maru dial holds context, permissions, decisions and unfinished work. Claude and Codex both work from it.

How I worked it out

It started as a way to keep my Flomaru and personal files and chats in order. Then I had my agents take stock of what I actually had. The core was spread across several folders, a few scheduled jobs had quietly stopped, and my instructions and memories had drifted apart between my two computers. So I drew one map, made sure every fact had one place to live, and picked a winner for when two sources disagree. That's when the workflow became a brain.

How it works

I keep the projects, the facts, the decisions, what's pending and who's allowed to do what in one place. Any AI chat, on either computer, reads it first, so I never explain the same thing twice. When it finishes something, it writes back what changed. Some of that it does on its own, and some it checks with me first.

Portfolio · BoardsHow the company brain stays current
Saved
Make plan

How the company brain stays current. The steps in order:

  1. Start: Everything about the company. Everything about my businesses goes in: projects, facts, decisions, pending work, roles and permissions. Before this it was scattered across chats, folders and two computers, and every new AI chat needed it all explained again.
  2. One living brain. It all lives in one synced set of readable files, with one place per kind of thing. Every fact has one owner, so there's one version of the truth.
  3. Any AI or person reads it. A new chat on either computer reads the map first, finds the project, then its instructions, pending work and shared rules. The files are the brain, and any AI is an interchangeable worker.
  4. Work gets done. The AI or person gets on with the job, working from the same truth as everyone else. When two sources disagree, my latest decision wins over older notes.
  5. Decision: Needs a yes?. Every action is checked against one permissions policy: what it can do alone, what needs my OK first, and what it never does. Scheduled runs only do what I've allowed them to do alone.
  6. Writes back what changed. At the end of every session, the AI writes back what changed. Finished work moves into the record that owns it, and replaced files are marked old, never deleted.
  7. End: Brain is up to date. The brain stays current as a side effect of the work, not because someone remembered to update it. The next chat picks up where the last one left off.

Where it stands

Maru started as a skill and grew into a workflow with its own automations. I run Flomaru, Rimaru and my own admin on it every day, from either computer. Any AI that opens it, as my assistant or my chief of staff, already knows where things stand. Next is making it a product, so other founders and small teams can run their own company brain.

Want to tell me what challenges you're facing?