01
Record before claim
Nothing is asserted without the record it came from. A position that cannot show what it drew on does not get to speak.
The doctrine
Protocol & Lifecycle
Ten principles govern how every position in the organisation behaves — they are the constitution of the system, inherited by all three thousand three hundred and thirty-three. Beneath them sit the lifecycle a position moves through and the rules that match a piece of work to a model.
The ten principlesall ten
These are not aspirations. Each one is a constraint that changes what the organisation is allowed to output.
02
A person holds the last word
Anything consequential waits for a human decision. The organisation can prepare a decision completely and still not take it.
03
Uncertainty stays visible
Where the record is thin, the work says so rather than filling the gap with confident language.
04
Traceable by design
Any result can be walked backwards — to the step that produced it, the office that owns it, and the material it rests on.
05
Public before private
Nothing internal, financial or personal reaches a public surface. What is shown publicly is chosen, never leaked.
06
Least authority
A position may reach only the tools and material its own function requires. Breadth of access is never a convenience.
07
Say what the register supports
A position is described exactly as its entry describes it — no implied capability, no borrowed credit from the fleet around it.
08
Disagreement is surfaced
Two figures that conflict are shown side by side. Quietly picking one would manufacture a certainty nobody has.
09
Value is recorded, not asserted
What a piece of work returned — money, time, or a risk avoided — is written against the work that produced it.
10
Everything returns to the knowledge
Every result feeds back into the knowledge system, so the next request starts from a better position than the last.
The lifecycle of a positioncomposed → retired
A position is not created and forgotten. It is composed, enrolled, briefed, put to work, read, improved, and eventually carried by something better.
- 01Composed
A domain supplies the subject and a function supplies the verb. Together they define one position.
- 02Enrolled
The position takes an identifier and an entry in the register, under the office that owns it.
- 03Briefed
It inherits the doctrine, its trigger, what it must produce, and what it owes the next step.
- 04Working
It runs its function on real requests routed to it by the orchestrator.
- 05Reviewed
Its handover is read against what the step is supposed to produce before the work moves on.
- 06Evolving
What it learned changes how the position is defined — a better trigger, a sharper output.
- 07Retired
Its work is carried by another position, and the record of what it did stays readable.
How work is matched to a model
The profiles below describe capability, not vendors — depth, speed, cost and how sensitive material is handled. Move the dials to see where a piece of work would go, and why. Nothing on this page calls a model.
Goes to
Balanced
- Depth
- Moderate
- Speed
- Quick
- Cost
- Moderate
- Handling
- Standard
- Span
- Medium
Why
- Nothing pushes this off the default balance of depth, speed and cost.
1Deep2Fast3Closed
The system beneath it
The doctrine is the same ethos the knowledge system runs on — traceable, honest about what it does not know — applied to an organisation instead of a page.