Everything in its place, and the place is arithmetic.
A page is right when its parts sum to twelve in each direction. Everything else — the rhythm, the hierarchy, the route the eye takes — falls out of that.
One protocol, every chain.
Messages move between chains without a bridge, a wrapped asset or a trusted third party. The security is configurable per application rather than inherited from the weakest link in a chain of them.
1.4 seconds to finality on the fast path, and the slow path is a configuration rather than a fallback.
Choose your verifiers, choose how many must agree, and change both without redeploying.
Send. Verify. Execute.
The endpoint takes a message and a destination. Nothing is wrapped and nothing is locked.
Your chosen verifiers attest independently. Quorum is a number you set, not one you inherit.
Built to be read, not decoded.
One function to send, one to receive. The rest is configuration that lives beside your contract rather than inside it.
Quoted before you send, in the token you send it with.
This row has no hairline above it, because it is the same subject continuing — the picture above is still speaking. Two rows read as one field, which is the second continuity device and the reason the page does not feel like a stack of boxes.
Four pictures, four crossings, one route through the page.
And it is all countable.
A bleed is a hand-off: it tells the eye where to go next. Two on the same side send it straight down one column — the path a reader takes anyway, and therefore the one worth nothing. Alternating, they zigzag, and the reader crosses the full measure at every step.
Side is measured, not declared — a cell is on the left if its centre is left of the page's. So the check cannot disagree with what is on screen, which is the failure mode of every rule that asks an author to restate what the layout already knows. Repeat a side and the overlay says so.