Routines: A Fixed Job, a Budget, a Pause Switch
Routines: A Fixed Job, a Budget, a Pause Switch
What a routine is: a scheduled agent with a written playbook, a daily allowance of computing time and a pause switch, started only when a program without AI finds work and given reference numbers rather than report text. The four routines that run today, the agent that looks after the build and test servers, and the two that are built but not yet switched on.
A
- A fixed job. It is written down as a playbook: a document that says step by step what a run does and what it must leave to a person. Changing what a routine does means changing its playbook, and that change is reviewed like any other.
- A budget. The routines share a small daily allowance of computing time. When it is used up, the work waits for the next day.
- A pause switch. A person can pause all routines, one routine, or one stuck item, for a set time of up to a week, or until further notice.
A routine does not run on a timer alone. Every quarter of an hour, a small program without AI looks for work. Only when it finds some does it start a fresh agent, and it hands over a list of reference numbers, never the text of a report. So a report cannot give orders to the agent that reads it.
Four routines run today. One works through feedback, one the system's own reports, and one contributors' requests. The fourth takes on larger fixes that the operations routine hands over as design work. An agent of the same kind looks after the servers that build and test the software. Each change a routine proposes starts with one line naming who asked for the work and which routine did it.
Two more are built but not yet switched on. One is a lead for each area of the work, such as mathematics or the app, which may start work nobody asked for, within a written charter. The other is a chief of staff that ranks the leads' questions for the people who answer them.