No king. The fabric draws itself.
The mesher draws the path
An orchestrator waits on a throne. Mesher does the other thing: it draws the next connection from the work that is already on the floor. Each node runs an instance. Each instance watches its neighbors, its load, and its health. It writes a mark. The next instance reads the mark. The path thickens. The fabric is the schedule.
That is the get. A persistent wiring entity reconstitutes after a crash the way a living root reconstitutes a trail. Its state is a durable record of health, wiring, and context. Its goal is one sentence: keep the mesh in shape. After a reboot the goal is still there. The archive the buyer owns still needs a way for facts and work to move. Mesher is how that motion stays alive — local instances, shared truth, connections that grow where they are used.
It watches the load that is here and the load that is coming. It draws a wire for that load. When the load moves, the wire follows. When a path goes quiet, the fabric thins. When a node wakes with work, the fabric thickens there first. The mesher is the hand that keeps drawing. The mesh is the page it draws on.
Four jobs that stay on
The optimizer has four jobs. They run together. They are the surface you can sit: a fabric that stays in shape because the same entity that drew the path is the entity that notices the path is dead.
- Optimal wiring. Choose physical and logical pathways so latency and bottlenecks do not own the day. Wire for the load that is here and the load that is coming.
- Efficient loading. Move compute and data so one node does not become the wait, and no node sits fat while another starves.
- Correct mapping. Keep a conflict-free picture of what is up — capacity, health, utilization — not a rumor of the cluster.
- Self-healing. Detect a broken path, a failed node, a leak, or a torn map, and restore it before the failure cascades.
A scheduler can place a pod and go back to sleep. Mesher’s claim is continuity. The four jobs do not hand off to a night shift. They are how a living wire stays a living wire: drawn, loaded, mapped, and repaired by the same persistent body.
Optimally wired. Efficiently loaded. Correctly mapped. Self-healing. That is the mission the fabric keeps.
A mark on the floor, one map
Every node runs an instance at the same time. Instances do not wait for a central signal. Each keeps a local view of neighbors, resources, and health. Shared truth arrives through CRDTs — conflict-free replicated types — so two nodes can update at once and still converge on one map. Leave a trace. Let the next instance read the trace. Let the global picture emerge from local marks.
That is stigmergy. A hypha does not phone the forest. It writes chemistry into the soil, and the next hypha reads the soil. Mesher writes the same way: a share, a health mark, a torn-link flag, a successful hop. Nobody carries the whole mesh in one head. Everybody influences the mesh the way a thread influences a cloth. Two updates land. The cloth is still one cloth.
The map is not a rumor you refresh on a dashboard. It is the definitive picture the next placement reads: what is up, what can still carry, what just failed. Correct mapping is the third job because the first two jobs are blind without it. A fabric that draws itself has to know where the ink already is.
Thick where the work lives
Work finds the thread that can still carry it, and that thread gets louder. Each node publishes a signed share of what it can still give — GPU, CPU, storage, VRAM — as a live percentage, not a brochure maximum. The share moves with the load. A floor keeps a node from vanishing. A ceiling keeps a node from promising the moon. Capability discovery probes the metal first, so the published share is a measured body, not a hope.
Routing follows that weather. A tensor job walks to the GPU whose cores and memory match the job. A low-latency signal job walks to the CPU that can still answer fast. Hot data stays on the fast tier. Warm data steps down. Cold data waits on cheap media until someone actually asks. The live topology graph is the cloth you can see: nodes for GPUs, CPUs, storage, and links; edges that light when a path is real and go dark when a path is gone.
Grade is how the cloth prefers a thread. Uptime, latency, power, and honor multiply into one score. A node that is brilliant on three axes and dead on the fourth does not win by charm. Work prefers the nodes that still hold. The 7-day window keeps the grade current. Yesterday’s hero that went quiet this morning is not still a hero.
Work writes a thicker thread. Quiet aisles stay thin. The fabric follows the load.
Heal, verify, place
The closed loop is three verbs. Heal finds the broken link, the failed node, the leak, and starts the repair. Verify checks that the map and the allocation are still true after the repair. Place moves the work and the configuration so the repair actually lands. Sense, admit, land. The distributor is Mesher: the piece that turns a verified heal into a new wiring.
A torn path does not wait for a pager. Helper dispatch sends a small, targeted fix — a retry, a failover, a cache evict — as a sub-entity with a scope, a trigger, and an end. The fix is idle, then active, then done. It does not become a second career on the node. If the first action misses, a fallback runs. If the fallback misses, the fix terminates and the loop starts again from a fresh mark on the floor.
That is why the four jobs are one organism. Wiring without heal is a drawing that yellows. Heal without verify is a rumor of a repair. Verify without place leaves the work on the dead aisle. The fabric draws itself because the same persistent body does all three, then draws again.
What the floor is looking at
Read this for the get: a persistent wiring entity, four jobs that stay on, CRDT maps, shares that follow the load, a live resource graph, and a heal–verify–place loop that lands a repair where the work already is. The sibling Living Mesh paper is the organism-level design — pheromone memory, partition as dormancy. This door is the optimizer that keeps that organism in shape. Mycelium Mesher is house wiring doctrine — not a Year-1 SKU. The P2P mesh in the house today is scaffolding. $20 million is an ask to put the first archives on customer hardware.
Sources: Trinity Sky, The Mycelium Mesher Entity (docs/whitepaper-mycelium-mesher/chapters/). Four jobs, CRDT shared truth, share voting, live resource map, and heal–verify–place are paper features. $20 million is an ask.