Teams do not usually fail because they forgot to draw enough boxes.
They fail because the boxes do not say what must be maintained. “Assess” becomes a meeting. “Observe” becomes a dashboard. “Plan” becomes a document. “Report” becomes a ritual. Everyone can point at the labels, but no one can quite say which living obligation each label is holding inside the organisation.
That is the quiet weakness of most operating models. They inherit department names as furniture. The names may be useful, but they are rarely lawful. They tell people where to sit, not what keeps the organism alive.
A four-corner board already helps. It says: do not mix public pattern, public event, private resource, and private metric as if they were the same kind of thing. Keep the shared pattern distinct from the live public event. Keep the private resource distinct from the private execution trace. Let the public seam be where shared pattern and live offer meet.
But a board can still feel like a template. It can still leave a reader asking: why these corners? Why this cycle? And if the board is real, who maintains it while work is actually happening?
4QX enters here as a stricter answer. It does not begin by inventing an org chart. It begins with the holon’s grammar: four corners, two loops, one public seam, and a six-step cycle of accountability. The working cycle can be named in operator language as Fit, Offer, Accept, Run, Publish, and Integrate. That is the rhythm by which a holon finds a possible action, offers it publicly, binds it to a pattern, runs it, publishes evidence, and folds the result back into its own state.
Full operator cycle on the dual field: Fit → Offer → Accept → Run → Publish → Integrate. (HOL-VIS-002)
The missing question: who keeps the board alive?
A static board can classify work. A living holon has to maintain itself.
That means each part of the board has a maintenance burden. The public pattern has to be assessed. The live public event has to be observed. The private resource has to be planned from. The private metric has to be reported back. The seam has to be coordinated. The traversals have to be delegated. The returns have to be revised.
Those seven words sound like departments, but the important point is the direction of derivation. The result is not “every organisation should have these seven departments because seven sounds complete.” The result is: once the four-corner board and its movement contexts are objectified, seven internal maintenance roles appear.
Think organs, not bureaucracy.
An organ is not a committee. It is a specialised maintenance power inside one body. The heart does not “represent stakeholders”. The lungs do not “own a vertical”. They keep a living relation possible. In the same way, the seven 4QX roles are better read as internal organs of a holon than as a civilisational model or a fashionable team structure.
From four corners to object-space
V3 gives the board: four corners arranged by public/private and form/flux. In general-audience language:
- Public Pattern: the shared structure, interface, schema, or reusable form.
- Public Event: the live offer, signal, or happening at the public seam.
- Private Resource: the holon’s internal resource, identity, capability, or commitment.
- Private Metric: the holon’s private execution trace, burn, evidence, or performance signal.
V4 asks a different question: what happens when that board becomes object-space?
The short answer is that each live distinction has to be held together with what it is not. An object is not merely one corner torn out of context. It is a distinction with its complement still present as support. Remove the degenerate void/whole distinction, the one that draws no live boundary, and seven live modes remain.
Four are the corner objects. Three are movement objects: Seam, Walk, and Merge.
That is the bridge from “four corners” to “seven organs”. Four organs maintain the object-places of the board. Three organs maintain the movement families through which the cycle runs.
The seven organs
In public prose, the department names are best treated as stable renderings. They are useful names for the maintenance powers, not proof that English itself was forced by geometry.
The seven internal roles can be read like this:
- Assess maintains the Public Pattern. It asks whether the shared pattern still holds.
- Observe maintains the Public Event. It attends to what is actually happening at the seam.
- Plan maintains the Private Resource. It prepares internal capacity for possible action.
- Report maintains the Private Metric. It returns execution evidence into a form that can be known.
- Coordinate maintains the Seam. It keeps public pattern and public event lawfully bindable.
- Delegate maintains Walk. It carries traversal and execution without pretending that all work lives in one point.
- Revise maintains Merge. It folds return evidence back into the holon so the next cycle is not blind repetition.
This is the first practical shift. “Departments” stop being boxes of people and become maintenance questions.
Who is keeping the public pattern honest?
Who is watching the live event rather than the plan?
Who is preparing resources without secretly steering execution?
Who is publishing metrics back into shared knowledge?
Who is keeping the seam clean?
Who is carrying delegated movement?
Who is revising the holon after the return?
A team may assign those powers to people, roles, software modules, agents, or rituals. That is implementation. The deeper point is that a running organisation needs all seven maintenance powers if its own grammar is to remain alive.
The cycle still comes first
The seven organs do not replace the six-step cycle.
A common misunderstanding is to treat V4 as a second phase system: first learn the six phases, then learn seven departments, then somehow reconcile two competing maps. That is not the intended reading.
The six-step cycle remains the temporal accountability rhythm: Fit, Offer, Accept, Run, Publish, Integrate.
Generic Organisation cycle for operators — clockwise from Fit. (HOL-VIS-003)
The seven organs maintain the object-space through which that rhythm can remain coherent. Four maintain the board’s object-places. Three maintain the movement contexts. In one cycle, the movement pattern can be read as Walk, Seam, Seam, Walk, Merge, Merge. Fit and Run traverse. Offer and Accept bind at the seam. Publish and Integrate return.
A worked example makes this less abstract.
Suppose a holon wants to adopt a new weekly publishing practice. Fit asks what continuity is actually possible from the holon’s current resources. Offer exposes a viable commitment at the public seam. Accept binds that offer to a reusable pattern. Run carries out the work. Publish returns evidence to the shared pattern. Integrate folds the result back into the holon’s private resource, so next week begins from what was learned rather than from the same fantasy.
The seven organs maintain that passage. Plan keeps the resource side honest before the offer. Observe keeps contact with what is actually happening. Coordinate keeps the public binding clean. Delegate carries the walk into execution. Report returns evidence. Revise changes the holon after the return. Assess checks whether the public pattern still deserves to be reused.
This is why the system is not merely an org chart. The names are subordinate to the maintenance powers. The maintenance powers are subordinate to the cycle. The cycle is subordinate to the holon’s need to remain coherent while acting.
What the machine-checked closure adds
The stronger claim is not that these seven English department names are culturally universal. They are not presented that way here.
The stronger claim is structural: after the V3 grammar is objectified, there are seven live complement-pair modes once the void/whole pair is removed. Each live object has a unique maintenance capability. The department face is where the closure is held. The capability face is how it is maintained.
That gives a lawful account of why the maintenance roles are not arbitrary.
The runtime claim is narrower. Full Generic Organisation closure depends on runtime-supplied evidence. The system must actually supply coherent cycle frames, seam-visible steps, replayable logs, phase coherence, recurrence from Integrate back to Fit, and decreasing H where work remains. V4 composes those frames and evidence. It does not manufacture them by naming departments.
That distinction matters. A team cannot draw seven boxes and thereby become coherent. It has to run the cycle, publish the evidence, and integrate the return.
What this does not claim
Evidence boundary: The structural seven-object result is machine-checked where named in the formal stack and synthesised in the Compendium. The runtime closure claim is conditional on supplied evidence. This article does not claim that any existing team, company, DAO, software agent, or governance process has achieved that closure merely by adopting these words.
It also does not claim that “society” here means a macro social programme. In this context, the society is internal to one holon: the internal plurality of organs that keeps one organism alive. The civilisational reading is not the job of this post.
Nor does it claim that the English labels Assess, Observe, Plan, Report, Coordinate, Delegate, and Revise are uniquely forced. They are a stable rendering layer over the maintenance roles. The formal weight sits under the objects and capabilities, not under the English vocabulary.
Why it matters
The practical promise is modest but sharp.
If an organisation only has departments, it can hide failure inside names. The report exists, but does it return execution evidence? The plan exists, but does it maintain real resource capacity? The coordination meeting exists, but does it keep the seam clean? The delegation happened, but did it carry lawful traversal or merely pass anxiety down the chain?
V4 makes those questions harder to dodge.
It turns “we have departments” into “which maintenance power is being held, for which part of the holon, in which cycle, with what evidence returning?” That is the move from an org chart to an anatomy.
And anatomy is a better metaphor than management fashion. A living holon does not need more boxes. It needs the organs that keep its distinctions, movements, and returns alive.
Compact summary
V4 adds object-space to the four-corner V3 board: after the void/whole pair is removed, seven live internal maintenance modes remain. These can be rendered as seven department-capabilities, but the English names are not the theorem. The point is that one holon needs four object-place maintainers and three movement maintainers if its Fit, Offer, Accept, Run, Publish, and Integrate cycle is to stay coherent. Runtime closure remains conditional on actual evidence, not on drawing seven boxes.
Read next
- Accountability Without Architecture Is Just a Promise – primer on the public seam and why accountability needs structure
- When Tension Actually Clears – how operational clearing depends on evidence, return, and integration
Co-writers
Body prose: GPT: 5.5.