Pick up almost any architecture diagram for a team, a product, or an AI agent stack. You will usually see boxes for “data”, “services”, “users”, and “metrics” – all on one canvas, as if inner planning and outer evidence were the same kind of thing.
That flattening is the problem this post addresses.
When private preparation, private execution, Public Pattern, and Public Event collapse into one undifferentiated map, accountability thins out. Work happens somewhere inside the system. Outcomes appear somewhere outside. The lawful path between them – what was offered, what was accepted, what ran, what was published, what was integrated back – becomes optional narration rather than structure.
4QX does not start with a bigger diagram. It starts with a smaller one that is harder to cheat.
Four corners, two kinds of work
Picture a square with four corners. Each corner is both a perspective (outer vs inner) and a modality (form vs flux). Name them in full before the shorthand sticks:
| Corner (first use) | Letter | Plain role |
|---|---|---|
| Public Pattern (top left) | P | Shared templates – what could be done |
| Public Event (top right) | E | Public activity – what is happening now |
| Private Resource (bottom left) | R | Private identity and capacity – who you are and what you hold |
| Private Metric (bottom right) | M | Private execution and measurement – what you actually burn |
Two naming traps worth fixing early:
- R is Private Resource, M is Private Metric – swapping them breaks the geometry.
- Outer is the top row (Public Pattern and Public Event – collective, seam-visible); inner is the bottom row (Private Resource and Private Metric – private to the holon).
This is not four unrelated departments. It is the minimal grid forced once you distinguish outer/inner and form/flux without adding a fifth corner.
Two triangles, not one loop
Two triangular cycles share the top edge of the square – the seam where Public Pattern meets Public Event:
Instance loop (inner-driven adaptation): Private Resource -> Public Pattern -> Public Event -> Private Resource. Three GO phases: Fit, Offer, Integrate (kernel: IStart, IDo, IFinish). Character: read the world, offer at the seam, integrate what returns.
Class loop (outer-driven execution): Public Pattern -> Public Event -> Private Metric -> Public Pattern. Three GO phases: Accept, Run, Publish (kernel: CStart, CDo, CFinish). Character: bind pattern to offer, execute privately, publish refined pattern back to the library.
Each triangle is three phases, not six. The full Generic Organisation cycle is six phases total, in this canonical order:
1. Fit (IStart) – prepare from integrated Private Resource 2. Offer (IDo) – expose a public offer at the seam 3. Accept (CStart) – bind shared Public Pattern to that offer 4. Run (CDo) – execute privately in Private Metric 5. Publish (CFinish) – publish results to the pattern library 6. Integrate (IFinish) – integrate back into Private Resource
Compendium geometry groups that sequence as 2-2-1-1: two Instance edges to initiate (Fit then Offer, before Accept), two Class edges to execute (Accept then Run, before Publish), one Class edge to publish (Publish), one Instance edge to complete (Integrate). That rhythm is proven necessary in the dual-triangle map, not stylistic preference.
The GO names and kernel names differ by layer; the edges do not.
The missing edge
There is no direct edge between Private Resource and Private Metric. Private Resource never talks directly to Private Metric.
That absence is the point.
If private capacity could reach private execution without crossing the seam between Public Pattern and Public Event, the system could change itself off-book. Audit trails would attach to symptoms, not decisions. Replay would corrupt hidden state. “Inner” and “outer” would become labels on a single fused engine rather than a structural distinction.
Forcing all significant effects through the seam (Public Pattern to Public Event) does four things at once:
- Accountability – nothing important skips public protocol
- Auditability – the history that matters is seam-visible
- Sovereignty – private spaces stay private, but they interact lawfully
- Idempotence – seam operations can be replayed without ghost state
In formal terms, this is the Seam-Topological Dichotomy named in Compendium `04_DUAL_TRIANGLE_SYSTEM`: direct Form-Flux adjacency exists only on the outer row (`Kernel.Geometry.row_direct_edge_iff_outer`). The inner row is mediated through the triangular loops, not a diagonal shortcut.
How to read the map without cosplay
The diagram is not decoration. Each label should earn its place in the prose around it.
- Use seam only when you mean the coupling between Public Pattern and Public Event – the public aperture.
- Do not import OODA or other four-step cybernetic frames; they are not part of 4QX.
- Do not draw six phases per triangle; Class is three, Instance is three, full cycle is six.
- When you show loops on visuals, pair geometry with the claim in the same beat – one diagram, one scope.
For a first visual, HOL-VIS-002 (dual-triangle seam, registered in the canonical anchor index) is the scoped asset: seam-only geometry, not an everything chart.
Why this map matters beyond notation
Software teams feel this problem in daily form: logs in one tool, tickets in another, model context in a third, “what we decided” in a fourth. Each surface looks authoritative locally. None of them is the seam where offer, acceptance, execution, and return are jointly visible.
Governance programmes feel it too: policies live in Public Pattern, incidents surface as Public Event, teams hold capacity in Private Resource, dashboards show burn in Private Metric – but the lawful chain from commitment to evidence is implicit.
The dual-triangle map is deliberately small. It is not trying to describe every box in your stack. It is trying to show where private work must become public before it counts as organisational reality – and where return traffic must cross back before it becomes part of who you are next time.
That is the whole game: two teloi, one seam, no back-channel.
Compact summary
Most architecture diagrams hide the boundary between private work and public accountability. 4QX names that boundary as the seam between Public Pattern and Public Event and shows two complementary three-phase loops – Class and Instance – sharing it. Private Resource and Private Metric never connect directly. The full cycle is six phases in canonical order, not six phases per triangle. The map is minimal on purpose: four quadrants, two teloi, one public aperture.
Read next
- Structural Sovereignty Is Not Enough – when governance infrastructure exists but Fit is not yet authored
- When a System Begins to Inhabit Its Own Law – operational continuity once the loops are inhabited
- 02_DUAL_TRIANGLES_AND_LOOPS – Compendium anchor for this map
Listen to understand more
Why Accountability Requires the Missing Edge (EN) · Geometría organizacional contra los atajos privados (es-419)
Co-writers
Cursor: Composer 2.5 (body and metadata wrap).