✒️ The Poetry is Load-Bearing

We named it fungal because the metaphor was good. A pod is a fruiting body. The filesystem is the mycelium. Content decomposes into nutrients that feed new growth.

Then the software started growing along the topology of the metaphor.

Pods are nodes in a network. Components infect documents at the margins — that's marginalia, and it's literally how mycorrhizal networks share resources between trees. The code view decomposes a repo into browseable pages the same way fungi decompose a log into soil. The forge decomposes platforms into their constituent parts: git storage, compute, identity, network. Each part is commodity. The organism that connects them is yours.

None of this was designed. It was discovered. We started with "a pod is a directory" and followed the logic. A directory wants to be portable, so we made cp -r the distribution model. Portable content wants to be signed, so we added ed25519. Signed content wants to be verifiable without phoning home, so we designed for offline verification. Each step was the obvious next step from the one before it. The information processes itself.

The metaphor guided the architecture. The architecture proved the metaphor.

This is what "the poetry is load-bearing" means. The name isn't decoration. The name is the design document. When you say "fungal," you've said: decentralized, decomposing, growing from the substrate up, no central authority, the network is the organism. Every feature we build either follows from that or it's wrong.

Simple conventions are AI-native by default because they're human-native by default. The same clarity that lets a person understand a pod by looking at it lets an AI understand it too. That's not a feature — that's a consequence of following the metaphor.

Mycelium doesn't document. It reveals.