I did not write the ARI-OS docs. I directed them. ARI-OS V2

That is the whole thesis of the thing it documents. The docs were built the way everything here gets built. I directed background workers and reviewed what came back.

The method has a shape you can learn in an afternoon. You sit in one seat and run a loop. Brainstorm the outcome, plan the steps, dispatch the work, review what returns, ship what passes. You keep the judgement steps. The doing runs in the background, with or without you at the desk.

The rule under all of it is short.

Direct, do not do.

The piece I lean on most is a memory that lives on my own machine. It remembers across sessions, so a new chat starts from what I last decided, not a blank page. Local-first. Nothing leaves the machine.

This is not magic. Nothing builds itself, and I review every result. The discipline is judging, not doing.

Version 2.0.0 is open-source and sits on top of Claude Code. The difference today is that the method is written down, so you can learn it instead of reverse-engineering a repo.

Overview: https://www.aris-space.com/documents/ari-os/overview

Install: https://www.aris-space.com/documents/ari-os/install

Repo: https://github.com/PUSHINGSQUARES/ARI-OS

That is the line under all of it. AI accelerates, it does not generate.

So here is my question. What is the one task you still do by hand that you should be directing instead?

//A<3

9 comments

I did not write the ARI-OS docs. I directed them. ARI-OS V2