1. Four work-stations
Take any project team (or neuron, or company) and ask two yes/no questions about every bit of information it holds:
- Question 1: Outer — is it shared by everyone? · inner — is it private?
- Question 2: Form — is it a stable record? · flux — is it happening right now?
Those two questions carve reality into four corners:
- TL (outer + form) – the library: shared playbooks, norms, CAD files.
- TR (outer + flux) – the marketplace: live task board, message bus.
- BL (inner + form) – your toolbox: unused parts, skills, free hours.
- BR (inner + flux) – your dashboard: sensor read-outs, code just pushed.
2. Two natural feedback loops
- Blueprint ⇄ Result runs on the diagonal library ↔ dashboard (TL ↔ BR)
- Capacity ⇄ Action runs on toolbox ↔ marketplace (BL ↔ TR)
Left alone these loops are just lines; they can spot gaps, but can’t tighten them.
3. Closing the loops with two “traffic-cop” corners
Drop a mediator peg on the top edge (library ↔ marketplace) and wrap each line around it:
Class loop TL → TR → BR → TL (Fire pivot at TR)
Instance loop BL → TL → TR → BL (Water pivot at TL)
Now each loop is a triangle:
- Class (Fire): publish recipe → burn it → log metrics
- Instance (Water): surface offer → commit job → receive ticket
Because both triangles share the bridge TL → TR, they lock together like two gears on one shaft.
4. What a cycle feels like from the inside
Class voice:
“I send a blueprint across the bridge, watch it run, and file the results back onto the shelf.”
Instance voice:
“I push my spare capacity up to the shelf, the market assigns me work, and the signed work-order drops back into my ledger.”
Same bridge, two opposite experiences.
5. Why focus is cyclic and why the lattice curls into a torus
Zoom in on any dashboard reading (BR) and you spawn a child square: {reading, {reading}}.
It inherits the same four stations, the same two triangles, the same top-edge bridge.
Sewing all those child squares onto their parents turns the tree of name-paths into a high-dimensional torus: a doughnut-of-doughnuts where every orbit is a closed focus loop that burns potential and writes its metrics upward.
6. Self-actualising geometry
No structure survives unless the triangles fire: patterns must be enacted and measured; resources must be offered and booked. Those twin cycles are the heartbeat that keeps the library relevant, the marketplace honest, the toolbox stocked, and the dashboard meaningful. Run them everywhere, at every scale, and the system continuously writes inner experience into collective knowledge—an automatic, fractal engine of coherence.