# ASI OS work methodology

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](start-here/what-this-site-covers.md), then read [How work is organised](start-here/how-work-is-organised.md).

## Where to go

**Start here**
What the site covers and the five-stage flow every piece of work follows. See [What this site covers](start-here/what-this-site-covers.md).
**Work structure**
The master rule, how an idea is routed to the right place, and how projects and programs are kept small. See [The master rule](work-structure/the-master-rule.md).
**Work families and phases**
The six phases of work, the catalog of document kinds and the front matter each kind carries. See [Phases and their routes](work-families/phases-and-their-routes.md).
**Processes**
Named, repeatable ways of doing one kind of work, and how the system picks one for you. See [The process catalog](processes/the-process-catalog.md).
**Knowledge and CRM**
How documents become knowledge-base articles, and how work links to people and organisations. See [Knowledge documents](knowledge-and-crm/knowledge-documents.md).
**Reference**
Terms, a process diagram and the record of decisions. See [Terms](reference/terms.md).

## See it in one picture

The [process diagram](reference/process-diagram.md) shows the guided flow applied to a real piece of work, with the two points where you decide.