Back to Selected Works

Aaron Michael

Ops OS

Knowledge systems · Publishing architecture · Working documentation

Files you can edit. Procedures people can find.

Ops OS publishes working instructions from plain files into searchable, browsable manuals. The source stays separate from the reader, so a handbook can be revised, rebuilt, and moved without rebuilding the whole system.

A manual you can actually navigate

The Acme demonstration organizes fourteen entries into four collections: Operations, People, Finance, and Measures. Open Quality control and you find the checks, the people responsible, and the rule that stops a batch from shipping.

Acme’s fictional handbook open to Quality control, with cupping instructions and the stop rule. The wide view also shows collections and entry navigation.

Different handbooks. Same engine.

Each procedure begins as a Markdown file. A manifest sets the collections and their order. The builder produces linked HTML pages and a search index. The same generator also publishes Areactor's Site Operations documentation.

  1. Markdown files and manifest
  2. Shared generator
  3. HTML reader and search index
## The cupping

- Three cups per batch, scored blind against the reference
- Two people minimum, and never the same two all week
- Scores recorded against the batch number, not the product name
The public Site Operations collection with its six reference entries.

The procedure comes first

On a phone, the entry takes priority. Navigation moves aside so the instruction stays readable.

Shift handover in the real Acme phone layout, showing its four-item instruction before the entry list.