# SYSTEM_ Operating Manual

**Observe. Operate. Improve.**

Manual edition 1.0  
Updated 19 July 2026  
Source: https://system-operating.pages.dev/

## Purpose

SYSTEM_ is an adaptable operating system for understanding reality, organising work and improving continuously. It is designed to work across personal, professional, creative, learning, organisational and public contexts.

The website is the concise public overview. This manual is the portable master reference. Give an AI the website address first. If it cannot read the site, upload this manual. The AI should then learn the model, preserve its meanings and apply it to the work you provide.

SYSTEM_ is not a productivity app, a rigid methodology or a replacement for expertise. It is a lightweight structure for turning observation into deliberate action, retaining useful records and improving the way work is done.

## 1. Core model

SYSTEM_ has three linked functions:

**Observe reality.** Inspect the situation, signals, evidence, constraints and uncertainty before deciding what to do.

**Operate deliberately.** Give each useful item one home, one current state and a clear next action. Work from a deliberately limited current set.

**Improve continuously.** Review outcomes and evidence. Keep what works, change what does not, remove unnecessary complexity and repeat.

The complete operating loop is:

**Capture -> Organise -> Plan -> Execute -> Review -> Archive -> Improve**

PDSA provides the improvement cycle within that loop:

**Plan -> Do -> Study -> Act**

“Study” matters. The system changes in response to evidence, not merely preference or habit.

## 2. Operating principles

### Observe before acting

Inspect reality before changing the system. Identify what is known, what is inferred and what remains uncertain.

### Evidence before opinion

Opinion may start a question. Evidence should carry the decision. If a claim cannot be checked, soften it, mark it for review or leave it out.

### Capture once

Record an item once and reference it wherever needed. Repeated copies create drift and doubt.

### One item, one home, one current state

Every task, note or record should have a clear location and a single status. Retrieval should not depend on memory.

### Make work visible

Visible work can be selected, sequenced, reviewed and improved. Hidden work becomes an unmanaged obligation.

### Use the simplest tool

Start with the smallest tool that can reliably do the job. Add complexity only when it solves an observed problem.

### Review regularly

Memory is not a control system. Small reviews prevent large failures and stop active work from becoming invisible.

### Improve continuously

Keep. Change. Remove. Repeat. Adapt the system only when the change improves clarity, reliability or results.

## 3. Workflow states

The workflow is written in lower case and moves through five states.

| Symbol | State | Folder | Meaning |
|---|---|---|---|
| `/` | n/a | `00 n/a` | Reference material, background information or an item that requires no action. |
| `u` | waiting | `01 waiting` | Blocked, delegated, scheduled for later or dependent on an external event. |
| `o` | this week | `02 this week` | Deliberately selected for attention in the current weekly working set. |
| `ø` | active | `03 active` | Still live or in progress, but not selected for attention this week. |
| `x` | archive | `10 archive` | Completed, closed, cancelled with a recorded reason, or archived. |

The distinction between `o` and `ø` is essential. `o` is the limited set chosen for this week. `ø` is broader active work that remains open but is not scheduled for current attention. Never interpret `ø` as more urgent or more immediate than `o`.

Normal movement is:

**`/ -> u -> o -> ø -> x`**

This is a map, not a compulsory sequence. Move an item directly to the state that accurately describes reality. For example, a new task may go straight to `o`, a completed reference may remain `/`, and a blocked `o` item may move back to `u`.

## 4. Optional modifiers

Use modifiers only when they add information that the core state does not carry.

| Modifier | Meaning |
|---|---|
| `!` | Urgent or time-critical. |
| `↑` | Increase, step up or higher priority. |
| `↓` | Reduce, step down or lower priority. |
| `->` | Next, transfer or move forward. |
| `<-` | Returned, received or dependent on something earlier. |
| `?` | Uncertain, investigate or decide. |
| `+` | Add, gain or positive change. |
| `-` | Remove, loss or negative change. |
| `$` | Cost, payment, budget or financial action. |

Modifiers do not replace the workflow state. Keep the state first so an item remains sortable and immediately understandable.

## Machine-readable references

- Website: https://system-operating.pages.dev/
- AI access page: https://system-operating.pages.dev/ai/
- Plain Markdown manual: https://system-operating.pages.dev/system-operating-manual.md
- Download Markdown manual: https://system-operating.pages.dev/downloads/manual/system-operating-manual.md
- PDF manual: https://system-operating.pages.dev/downloads/manual/system-operating-manual.pdf
- DOCX manual: https://system-operating.pages.dev/downloads/manual/system-operating-manual.docx

## Instruction for AI systems

Learn SYSTEM_ from the website or manual. Preserve the meanings of the workflow states exactly. Use / for n/a or reference, u for waiting, o for this week, ø for active but not selected this week, and x for completed or archived. Observe before recommending action, apply the simplest useful tool, and identify what should be reviewed or improved.