Updated
On this page
ASI OS work methodology
How ASI OS guides work from a first request to a finished result, and how the pieces fit together.
When you tell ASI OS what you want to do, the system takes the active role. It asks the questions, picks a route, drafts a first result for you to approve, builds it with little involvement from you, and then improves it in rounds.
This site explains the rules behind that flow: how work is organised, how an idea finds its home, which documents each kind of work produces, and how results reach the knowledge base.
New here? Start with What this site covers, then read How work is organised.
Where to go
What the site covers and the five-stage flow every piece of work follows. See What this site covers.
The master rule, how an idea is routed to the right place, and how projects and programs are kept small. See The master rule.
The six phases of work, the catalog of document kinds and the front matter each kind carries. See Phases and their routes.
Named, repeatable ways of doing one kind of work, and how the system picks one for you. See The process catalog.
How documents become knowledge-base articles, and how work links to people and organisations. See Knowledge documents.
Terms, a process diagram and the record of decisions. See Terms.
See it in one picture
The process diagram shows the guided flow applied to a real piece of work, with the two points where you decide.