The Operations Center
One task, end to end. A request arrives as language, is read and routed to the office that owns it, planned into steps, run by the positions in that domain, read against what it was supposed to produce, signed off by a person, closed, recorded, and returned to the knowledge system.
The cycle13 stages
Thirteen stages, grouped into five acts. Select an act to see which stages belong to it, then open any piece of work below to follow it all the way through.
A request arrives as language and leaves as an addressed task.
- 01Received
- 02Read
- 03Routed
- 04Context gathered
- 05Planned
- 06Running
- 07Reviewed
- 08Awaiting sign-off
- 09Signed off
- 10Closed
- 11Value recorded
- 12Logged
- 13Learned
What the operator sees
- Needs a personThe plot appraisal reconciliation is waiting on the Chief Development Officer.09:44
- Value recordedThe resident wellbeing briefing closed — recorded as time saved.09:12
- Handover shortPartnership triage has not yet named an intent or a domain.10:22
- Disagreement foundA sustainability claim has nothing standing behind it — flagged, not removed.08:16
The rhythm it runs on
The organisation is tuned to a human day rather than a machine clock — intention in the morning, execution through the day, reflection in the evening. The same shape repeats across a project’s life and a resident’s.
Intention
The day is framed against what the domain is actually for.
Execution
Positions run their functions on the work routed to them.
Reflection
Handovers are read, value is recorded, and what was learned returns.
Load across the organisation12 of 33 shown
Every domain carries the same hundred and one positions, so capacity is even by construction. What differs is what arrives.
What the system reports on itself
Read from the register
3,333 positions across 33 domains, each running the full 101-step chain. These figures are the organisation as designed.
Measured per task
The cycle records a timestamp at every stage, so how long each act takes is a property of the record rather than an estimate.
Written against the work
Each closed task carries the kind of return it produced and the basis for saying so — money, time, or a risk that did not land.
The four pieces of work above are worked examples: real shapes, real routing, real handovers, so the cycle can be read as something that happens rather than something drawn. The audit trail is where the record of the whole cycle lives.