Watch a team that ships constantly. Standups happen. Tickets move. Slack stays loud.
And yet the same arguments return. The same backlog reshuffles. The same “we’ll integrate that later” note survives every sprint review.
That feeling is not laziness. It is often incomplete cycle: activity without closure.
This post names the rhythm that turns motion into settlement â six organisational steps that map directly onto the formal six-phase kernel. Geometry is assumed from Accountability Without Architecture Is Just a Promise; here we add time and operator names.
Six names, one lawful order
Generic Organisation uses six plain verbs in fixed order:
Fit â Offer â Accept â Run â Publish â Integrate
This is not a checklist you can reorder for taste. Under the dual-triangle constraints, a complete cycle is exactly these six moves â the formal project proves there are no exotic shortcuts.
Think of it as an operating rhythm, not a methodology poster:
| Step | Loop | Plain job |
|---|---|---|
| Fit | Instance | Read your own context and prepare what could continue |
| Offer | Instance | Expose a bounded commitment at the public seam |
| Accept | Class | Bind shared pattern to that commitment |
| Run | Class | Execute privately against the accepted binding |
| Publish | Class | Return witnessed evidence to shared structure |
| Integrate | Instance | Fold the return into who you are next |
Two loops, three phases each, six phases total â not six phases per loop.
What each step is doing (without kernel jargon)
Fit â Before anything public happens, the holon matches inherited state to possible continuations. Without Fit, patterns do not meet context; work starts from fantasy.
Offer â Self-change becomes seam-visible. A commitment others can see, accept, or refuse. Without Offer, intention stays private wish.
Accept â Shared pattern locks to the offered commitment. Offer and Accept are two faces of one public seam event: expose, then bind. Without Accept, commitments starve for lawful pattern.
Run â The accepted binding executes in private metric space â the burn that actually happens. Without Run, change stays narrative.
Publish â Results and witness return to public structure so learning accumulates. Without Publish, teams repeat the same surprise.
Integrate â Returned evidence rewrites private identity so the next Fit starts from truth, not from the old story. Without Integrate, results dissipate â busy forever, settled never.
That last row is the headline failure mode behind “we’re always busy but nothing sticks.”
Two lifecycles, one thread
Interleave the loops and the same six names tell two stories:
Instance (named continuity): Fit â Offer â ⦠â Integrate â next Fit
Class (named pattern): ⦠â Accept â Run â Publish â â¦
Instance carries the thread of “who we are becoming.” Class carries “what pattern we test and refine.” They meet at the seam (Offer/Accept), then separate for Run and Publish before Instance closes the loop at Integrate.
Cybernetic closure in one line:
> Integrateâ â Fitâââ
The current starting surface is made of prior integrates. You do not first exist as a finished team and then organise; you persist by folding returns into the next availability.
Which phase is missing?
Before adding process, diagnose which step was skipped or conflated:
| If this is weak⦠| You often see⦠|
|---|---|
| Fit | Plans detached from actual capacity and context |
| Offer | Decisions made in side channels; surprises at review |
| Accept | Commitments without binding agreement; scope drift |
| Run | Tickets closed without execution; theatre of progress |
| Publish | Learning trapped in individuals; repeated mistakes |
| Integrate | Closed work that never changes how the next cycle starts |
Conflation counts as skip. “We offered and accepted in the same meeting” without seam-visible binding is not a shortcut â it is missing lawful coupling. “We shipped” without Integrate is Publish without closure.
How this connects to tension clearing
Harmony posts name what must drain: structure debt and continuity debt summing to H. This post names how work is supposed to move so that draining can happen â lawful steps through the cycle rather than backlog cosplay.
Class-side steps (Accept, Run, Publish) mainly refine shared pattern. Instance-side steps (Fit, Offer, Integrate) mainly process continuity. Confusing which side you are neglecting sends fixes to the wrong loop.
A Monday-morning question
Before the next standup adds motion, ask:
> Which phase did we skip â and what would Integrate have changed for next week’s Fit?
If nobody can answer, you are measuring activity again, not settlement.
Compact summary
Busy teams often lack closure, not effort. Six steps â Fit, Offer, Accept, Run, Publish, Integrate â are the minimal complete organisational cycle: two three-phase loops interleaved into one lawful sequence. Skipping Integrate is a common pattern: work finishes in name only while the next cycle starts from unchanged identity. Name the missing phase before adding more process.
Read next
- Accountability Without Architecture Is Just a Promise â the seam map this rhythm runs on
- 03_SIX_PHASE_CYCLE_AND_TIME.md â canonical order, seam event, six-move normal form
- 07_GENERIC_ORGANISATION.md â GO rendering and why every phase is necessary
Listen to understand more: Why Busy Workflows Never Settle
Co-writers
Cursor: Composer 2.5 (body + metadata â Gate 0 passed 2026-06-14).