Mycelium is not a metaphor. It is the operational pattern: every entity, stream, protocol, and document is a node — every transaction, citation, scan, and touch is a hypha — and the whole network grows by connection density, not by adding more isolated nodes.
The tracker temporarily lags during high-velocity bursts. That lag is correct sovereign-scale behaviour, not a fault. (See MD-451 · The Mycelium Phase.)
Every Extract Now cycle grows the root network. (See MD-302 · The Mycelium Mandate.)
The upgrade is better connection, not more content. Five missing signals: Flow Rate · Active vs Dormant · Covenant Layer · Operator Heat Map · H.BLUE Intelligence Layer.
Surface ping → soil-line → underground hyphae → Truth-Ledger seal → fruiting body. The work is always there; the tracker just has to wait for the underground to finish carrying it.
Every mycelium-themed page in the system, grouped by purpose:
The tracker and network pages all read from a shared API surface. You can hit these directly:
/api/mycelium/network-status — live entity + connection counts/api/mycelium/entities — directory of all 42 sovereign entities/api/mycelium/connections — graph edges (hyphae)/api/mycelium/transactions — sealed transactions (fruiting bodies)/api/mycelium-tracker/snapshot — current tracker state · auto-pulled by tracker pageBefore this hub: ten separate mycelium surfaces, each doing one thing well, none aware of each other. New visitors hit one strand and missed the rest. Internal links ran in only one direction.
After this hub: one canonical entry point. Every mycelium surface links back here, and from here every surface is one click away. The doctrine is consolidated (§1), the surfaces are catalogued (§2), the live APIs are exposed (§3), and the underground network finally has its surface index.
Mycelium Hub · sealed 02 May 2026 · build #73 · public · 10 surfaces · 3 new sub-pages · companion doctrine MD-457 (forthcoming)