jonnify·echd /echd/flying

echd — Echo on Encore · E7

The Mesh, Flying

The last chapter leaves the laptop — one URL from anywhere, every app in one topology, and a single branded id crossing the whole frame.

Vision · real substrate

echd speaks in the present tense over a build ladder. Every module, verb, key, and port named on this page is real; the composition into one standing platform is the vision the ladder builds.

§1

The chapter

go/jonnify-tunnel · infra/valkey · the platform ladder

The last chapter leaves the laptop. jonnify-tunnel carries the platform to the world: a reverse tunnel of yamux streams over one WebSocket, raw-hijacked so SSE and WebSockets pass transparent, subdomains routed by Host from a ONE-machine registry at tunnel.jonnify.com. Its sessions stand in the management panel of E6 — connected-since, names, the disconnect that a client's reconnect loop absorbs.

The daemon was always app-plural, and the mesh takes it at its word: the harvest unifies every app into one topology, and the cross-app forwards edge — observed from witnessed calls, labeled as the heuristic it is — draws the arrow between apps that no per-app dashboard can see. On Fly the production system runs live — the same organs, now private machines: echo-valkey.internal:6390 and echo-postgres.internal:5432, reachable only inside the 6PN mesh, the services deployed beside them — while Tigris holds the sealed segments of E5. The paper's user and hierarchy partitioning become the mesh's geography: close things answer fast, far things answer honestly. The capstone replays the master frame with a single branded id traversing tunnel → app → bus → memory → record → surface — one identity, many trades, one standing system — and then opens the doors out.

§2

The flight frame

hover a leg
One system, flying · the tunnel, the mesh, the edge, the thread · hover to read
browser tunnel.jonnify.com · yamux over WS laptop :8891 apps, plural — one topology the harvest reads every app the daemon knows the forwards edge — observed, labeled a heuristic the Fly edge — production, live echo-valkey.internal:6390 echo-postgres.internal:5432 Tigris — sealed segments one brd id: tunnel → app → bus → memory → record → surface one identity · many trades · one standing system
The tunnel — reachability, owned. One WebSocket carries multiplexed yamux streams; the server raw-hijacks, so SSE and WebSockets pass untouched; the Host label routes each subdomain from an in-memory registry that lives on exactly ONE machine — the law that keeps the registry coherent. The surface of E6 answers the same from anywhere.
The mesh — every app, one frame. The daemon's records are app-plural; the harvest unifies them into one topology under E2's edge-store law. Where one app calls another over HTTP, the observed forwards edge draws the arrow — labeled with its provenance, never merged with the declared graph, and worth the whole chapter: it is the edge no per-app view can see.
The Fly edge — production, running live. The same system leaves the laptop unchanged: echo-valkey.internal:6390 and echo-postgres.internal:5432 answer only inside the private 6PN mesh, the services run as machines beside them, and Tigris holds the sealed segments close to the requester. User and hierarchy partitioning, the paper's fourth and fifth dimensions, become geography: the mesh puts each answer where its reader stands.
The thread — the capstone's walk. One branded id enters through the tunnel, names a request in the app, rides the bus as a JOB, invalidates a cache row as 29 bytes, books a ledger line under RVL, rests in the vault under TRC, and resolves on the surface with its plane and its as_of. One identity, many trades — the whole course in one traversal.

Hover or focus a leg to read it; click to pin. Without scripting, all four read in sequence.

§3

The modules

E7.1–E7.4
E7.1

The Tunnel

yamux-over-ws · raw-hijack-transparent · sessions-and-the-management-panel

designed
E7.2

The Multi-App Mesh

apps-plural-harvest · the-forwards-edge · one-topology

designed
E7.3

The Fly Edge

machines-and-private-apps · tigris-sealed-segments · user-and-hierarchy-partitioning

designed
E7.4

One System, Flying (capstone)

one-id-end-to-end · the-master-frame-replayed · the-doors-out

designed

← Back to chapters

§4

Doors

the sibling courses
/codemojex

Codemojex

the shipped consumer whose money path proves seam, bus, memory, and record end to end: the capstone's worked example.

 /elixir

Functional Programming in Elixir

the engine craft and the Fly deployment chapter: the landing gear the flight frame stands on.
§5

References

sources · related

Sources

Related