Skip to main content
Handbook/Automate/Page 74 · Unification

One System for Everything

Share

Share this page

Pass it to someone who needs it.

Star on GitHub

Key takeaway: Put everything in one file tree

Your plans live in one app, your tasks in another, your notes in a third, and your agent can open none of them. This chapter puts your whole operation into one tree of plain files on your machine, so nothing that runs your work is hidden from the thing doing it.

9.2.1One tree, not ten apps

Everything about your operation lives in one folder tree on your machine: your plans, your tasks, your notes, your decisions, and the app itself. Not a docs app, a task app, and a chat thread each holding a piece.

The reason is blunt: your agent can open a folder. It cannot open your Notion, your task app, or your memory of what you decided last Tuesday.

operating-base/ plans/ roadmap.md tasks/ todo.md decisions.md app/ (your actual application code)

That is day one. A production tree grows branches you will build through this part: reports the agents write, skills they load, a log of everything that happened.

9.2.2Everything is a plain file

Every piece is a plain text file, usually markdown, which is just plain text with light formatting. Not a document locked inside some app's format.

A plan is a text file. A task list is a text file. A decision is one line in a text file. That is exactly what your agent reads and writes on its own, and what you can still open in ten years when today's apps are gone.

Hint: some people formalize this into a shared convention, so every agent reads a knowledge base the same way. One is the Open Knowledge Format: markdown files plus a few shared rules for how each file is labeled. You do not need a spec to start, but it is a useful reference once your tree grows.

9.2.3One source of truth

Because it is all one tree, each thing lives in exactly one place. Your current priorities are one file, not three half-remembered versions in your head and two apps.

When something changes, you change it there. Every agent that reads it then sees the same truth, with no syncing and no "which copy is right."

Change the one priorities file and every agent that reads it sees the same truth.

9.2.4Why one system beats many

Ten apps mean ten silos your agent cannot cross, and a full picture only you can hold, in your head. One tree means the agent sees everything, moves work between the parts, and misses nothing.

It is also yours. Plain files on your own disk are portable, backed up alongside your code, and never locked inside someone else's cloud.

This prompt does the first move for you, and sets the rule that keeps the tree one tree:

Ready prompt
Act as a senior engineer starting my one system. Read my rules file and my operating base README so this lands where it belongs. I will name one thing I currently track somewhere else. Move it into a plain text file inside my operating base, in the format the rest of the system will use, and tell me what I can now stop opening. Then record in my rules file that this tree is the single source of truth for how I run things, and that new tracking goes here as a plain file rather than into another app. If you need the full reasoning behind this step, read https://zalt.me/guides/vibe-coding/ai-os/unified-system The one thing I track elsewhere today:

Do this now: paste the prompt and move one thing out of another app and into your system. That file is the start of the tree.

Mahmoud Zalt

Mahmoud Zalt

Software engineer, 16+ yrs · built Sistava.com in 3 months, idea to production, using these methods

Resources
Star on GitHubContribute
Donate

Support my work

A small tip keeps the free work coming.

© 2026 Mahmoud Zalt. Free to read, not to republish.
Copyright & license