FIG. V // THE STACK AT 100 FEET

Sixty-two chains go in.
One value comes out.

Everything below the waist is aggregation — mechanical, per-chain, and it needs nobody's agreement. Everything above it is universal. The waist is the only place in the system where independent parties must converge on a single value, and that is what a coordination layer is. It is also the one layer not yet decentralised.

01 // WHAT CHANGED, AND WHY

The nine-layer list was a pipeline, not an architecture

A flat stack of nine equal bands is easy to draw and it hides the three facts that matter. Each correction below changes what the picture argues.

The shape is an hourglass, not a ladder. Band width now encodes how many independent values exist at that layer. Sixty-two at the bottom, one at the waist, many again at the top. Convergence is the product, so convergence should be the silhouette — not a bullet in a caption.

The proof is not a layer, it is a vertical cut. The V5 blob's six fields are slices taken at six different heights of this diagram — the superroot at the waist, the chain header at the floor, twig siblings in the middle. Drawing PROOF as a band above ANCHOR implied it sits on top of the stack. It runs through it. Switch to the proof lens and watch the tap points light.

Anchoring goes sideways, not up. Base is not the layer above the superroot; it is an external surface the superroot is published to. Drawn as a band, it reads as a dependency the stack rests on. Drawn as an outbound commitment, it reads as what it is — and it makes the honest scope legible: an anchor protects the prefix it published, not the epochs after it.

Three zones, not nine peers. OBSERVE is untrusted input. ACCUMULATE is mechanical and needs no agreement — any honest machine gets the same answer. AGREE is where trust is manufactured. Only the third zone is a consensus problem, and separating them stops a reader assuming the whole stack is one.

02 // WHY THIS IS A COORDINATION LAYER

The waist is the whole claim

“Coordination layer” is usually a word people reach for when the thing is hard to describe. Here it has a test, and the diagram passes or fails it visibly.

coordination = the point where n independent parties must converge on one value

Below the waist, nobody needs to agree with anybody. A twig root is a function of block headers — two honest machines compute the same one, and if they differ, one is simply wrong. That is aggregation, and it is not a consensus problem.

At the waist, sixty-two per-chain roots become one superroot, and there is exactly one of them. Every party downstream — a contract on Base, an agent on the CLOB, a hosted Cubicle strategy — inherits that single value. They are coordinated by construction, because there is nothing else to be coordinated on.

And it is the one gap

Today the waist is computed by a single indexer on a ten-second timer. Everything beneath it is independently checkable; everything above it inherits whatever that one process decided.

today: computed
the lattice: agreed

That is not a weakness discovered in review — it is the product. The lattice sits at L4 precisely because L4 is the last layer holding many independent values and the first producing one. It is the only place a quorum can do any work.

Which is also why the status lens is worth showing to a technical investor rather than hiding: eight layers read REAL, one reads PROPOSED, and the one that reads PROPOSED is the one being raised for. A stack diagram where everything is green is a diagram nobody believes.

03 // HOW TO SHOW IT

One diagram, four readings

Three audiences want three different things from the same picture, and shipping three diagrams means maintaining three diagrams and confusing anyone who sees two. The lens switcher is the cheaper answer: the geometry never moves, only the emphasis and the annotations do, so a reader who has seen one lens can read the next without relearning the shape.

Architecture — the default, and the one that goes in the deck. Answers “what is this”. Nobody is asked to trust anything yet.

Where a proof comes from — for anyone integrating. Traces one transaction from the floor to the waist and back out as a blob, lighting the six tap points. This is the lens that converts a sceptic, because it is checkable in thirty seconds with no wallet.

Where you plug in — for operators. Two bands light: run a collector at L1, attest at L4. Everything else greys out. The recruitment surface is the dark cells, and it works because absence is a hashed leaf rather than a missing row.

What is actually built — for investors and diligence. Real, Building, Proposed, per layer, using the same tagging discipline as the whitepaper. One tag reads PROPOSED. That is the ask.