Can it turn on the routine it proposes?

No. A proposal is inert until a named person accepts it. An accepted routine then runs the way any routine does, with sign-off on every cycle, as the plans and routines entry and the approval gates entry describe.

What if it is wrong about what counts as busywork?

The proposal carries its evidence, so the person can see why it was raised. They decline it, the decline is recorded, and the same observation is not raised again unchanged.

When the system notices your busywork before you do

The record of governed work already shows the busywork nobody put on a list

Today

A process list built from whoever spoke up

The work that eats a week is rarely on any list, because nobody decided to do it.
It accreted: a check somebody started doing before a step, a hand-off made by hand every cycle.
The person doing it is the last to see it as a process, because to them it is Tuesday.
Asking people what they would automate returns the answers they can already see.

With agents

Proposals from the record, inert until accepted

Candidates come from the record instead of from memory.
Nothing is automated because a system suggested it.
The scope of what is watched is stated and narrow.

The observation pattern and its scope

Observation is a pattern in which a system that already governs a work record finds busywork inside it and proposes something for a person to decide on. The scope comes first.

01

The data scope is the work record the system already governs

Work orders, cycles, hand-offs, sign-offs. Nothing outside it: no inbox, no chat, no calendar, no activity on anyone's machine.

02

Busywork is repeated, low-judgement, regular work that nobody wrote down as a process

All three properties are required. Repeated work that needs judgement is out; irregular work cannot become a routine; work with a written process is already governed.

03

An observation is a pattern found in that record, carried with its evidence

The same shape of task recurring on a cadence, the same hand-off made by hand each cycle, the same check before the same step. The observation is an artifact: what was seen, where, and the runs that show it.

04

The system proposes; it does not act

An observation becomes a proposed routine or a proposed work order, with the evidence and a stated reason attached. Nothing is created, scheduled or changed by the proposal itself.

05

Human gate

A named person reads the proposal and accepts it, changes it, or declines it. Declining is recorded, so the same observation is not re-proposed every cycle. How It Works describes what an accepted proposal becomes once it is governed work.

06

Being noticed does not make work ready

An accepted proposal enters the same readiness sorting as any other candidate, and the readiness checklist is where that happens.

07

Observations that describe judgement work are surfaced as findings rather than proposed for automation

Some repeated work belongs with a person, and the entry on work that should stay human owns that boundary.

Results

What changes when the record is what gets watched

Candidates with evidence attached

The observation is drawn from work already recorded, with the evidence attached, so the list is built from what happened rather than from who spoke up.

No authority in a suggestion

A proposal is inert until a named person accepts it, and declines are recorded, so a suggestion carries no authority of its own.

A narrow, stated scope

The data scope is the governed record, written into the pattern rather than assumed.

Where this fits

Concept

This is the entry the library points at whenever work is found inside the governed record rather than requested from outside it; proactive drafting is the outside-in sibling, and the plans and routines entry defines what a proposal becomes. The Platform page is the way up from here. How It Works describes how governed work is recorded, and that record is the only thing this pattern reads.

AAOS Platform

How It Works

Questions, answered

It reads the governed work record: work orders, cycles, hand-offs and sign-offs. It does not read a person's inbox, chat, calendar or activity. If the work was not recorded as governed work, the system cannot see it.