Those dots are cool, but every vibe-coded site has them now. Change them or remove them.
My AI system is a folder.
AIOS is the system I run my research, engineering and production on, built on Claude Code. What it knows is written down as files it can read, check and correct, so nothing important lives in a chat that scrolls away.
Open it yourself.
The real folders, with what each part does. Anything about money, health or other people stays locked.
How a session runs.
- Start
The state loads first.
A hook syncs with the other machine, then puts the current focus, open decisions, next tasks and lessons in force into the session before I type a word.
- Route
One owner per job.
Every request goes to exactly one skill, the newest and most capable one. Two half-working ways to do the same thing never exist side by side.
- Work
Subagents keep the main session clean.
Research runs in isolated researcher agents that return a graded brief. Consequential output gets a fresh-context check before it leaves the machine.
- Write
State is written down precisely.
Records go through a command line that validates each one and checks its revision, so two sessions cannot overwrite each other.
- Stop
The turn ends in Git.
When a turn ends, a hook commits the changed work, merges the other machine and pushes. If anything refuses, the session has to fix the cause.
A correction, made once,
becomes a rule.
A real example from 20 October 2026. I said one sentence about this website; here is everything that followed.
A lesson with its trigger, its scope and the evidence: records/lessons/no-glowing-status-dots-on-filip-sites.json
In the same turn, one line for the design skill. Nothing changes until I approve it.
Approved, the lesson is verified and the rule loads in every later session, on every machine.
words in headlines, numbered 01/02/03 section labels, monospace eyebrow labels, pill buttons- everywhere. No eyebrows/kickers on new builds by default.+ everywhere, coloured status dots and dot-plus-label pills (put status in plain spec data).+ No eyebrows/kickers on new builds by default.
What it never does on its own.
Routine work runs without asking. These always wait for a clear yes from me, every time.
SendingNothing is sent, posted or published in my name without my approval of that message
MoneyNo purchase and no paid model run without an approved ceiling
CodeNo third-party code installed or updated without asking
AccessNo account, credential or permission change; credentials are never printed
TruthIt reports only what a tool verified in this session and labels the rest unverified
MemoryOne source per fact, archived and never deleted
What it runs on.
Claude CodeSessions, skills, subagents and hooks
PythonA command line for records, recall and the research library
Git and GitHubOne private repository, two machines, every turn checkpointed
MCP serversResearch across Reddit, X, Instagram and papers; ComfyUI; Roblox Studio
TestsIncluding a budget that keeps the instructions short enough to be followed
Building agents for real work?
I design systems like this for teams: memory that is files, one owner per job and corrections that stick.