Sap Flow

When people talk about shared fictional universes, the default mental model is a corporate hierarchy. There's a parent franchise at the top, and subsidiary projects underneath. The parent constrains the children. Marvel controls what the individual films can establish. Tolkien's estate controls Middle-earth. The Star Wars story group controls what's canon across all the novels, shows, and games.

This model captures something real: shared universes do constrain individual projects. You can't write a Star Wars novel where the Force doesn't exist. But the hierarchy model misses half the picture. It treats the shared universe as something that flows downward, from the top, imposing constraints on the creative work below. In reality, the flow runs in both directions. The shared universe is richer than it was at the start not because someone at headquarters expanded it, but because every individual project contributed details, events, and texture that enriched the whole.

The MCU's universe-level canon is vastly more detailed than it was in 2008. That detail didn't come from a master plan executed from the top. It came from hundreds of creative decisions made within individual films that propagated upward into the shared world. Each movie established facts that all subsequent movies inherited. The creative work at the edges is what made the center grow.

The tree model

The governance framework I've been developing for the Transmission Zero universe uses a different model: a biological tree with bidirectional flow. It's not just a metaphor. The structure maps directly onto how governance works in a multi-project world.

The root system is the shared universe canon. Physics, species biology, deep history: the foundational substrate that all projects depend on. This is what makes the projects part of the same world rather than unrelated stories. In Transmission Zero, the root system includes the laws of physics, the existence and evolutionary baselines of each sapient species, the fact that the bubble happened and isolated Earth, and the structural principles that apply universe-wide (like "no species is more evolved than another" and the anti-monoculture commitment).

The trunk is the shared continuous history. Everything that happened in the universe up to the point where individual projects branch off. In Transmission Zero, the trunk carries the deep history of interstellar civilization, the formation of multi-species community, the development of trade and political institutions, and the isolation and reintegration of humanity. All projects share the trunk.

The branches are where projects diverge. Two projects set in the same era at the same location share a long branch (lots of shared canon between them). Two projects set in different eras on different sides of the galaxy share only the trunk and roots. The Transmission Zero tree currently has two branches: the bubble/contact stories, set during Earth's isolation and first contact, and the medical drama, set two to three human generations after the bubble ended. These two branches share the entire trunk up to the bubble era, then diverge.

The leaves are the individual projects themselves, where creative work actually happens. Each leaf has its own internal canon hierarchy: its own foundational commitments (genre, tone, cast, format), its own established and working canon, its own space for exploration and divergence.

Two directions of flow

Here is the part that makes the tree model essential rather than decorative.

In a real tree, sap flows in two directions. Water moves from root to leaf, carrying minerals from the soil. Sugar (produced by photosynthesis in the leaves) moves from leaf to root, feeding the root system and enabling further growth. Both flows are necessary. A tree with roots but no leaves can't grow. A tree with leaves but no roots can't stand.

In a shared fictional universe, the flows map cleanly.

Root to leaf: constraint. The shared universe canon feeds each project with the substrate it needs. The physics. The species biology. The shared history. Every project must be consistent with the root system. A story in the medical drama can't contradict the established biology of Species B, because that biology lives in the roots, shared by all projects. This constraint is what keeps the projects coherent as parts of the same world. Without it, they'd just be unrelated stories with similar proper nouns.

The constraint flow is like water: essential, nourishing, and directional. It flows from the deepest shared commitments outward to the most specific creative work. Each project inherits everything below its branch point.

Leaf to root: contribution. The projects do the creative photosynthesis. When a medical drama story establishes something about Species B's joining biology in clinical detail, that detail (if it's about the evolutionary baseline rather than a project-specific cultural encounter) enriches the root system. It becomes available to all projects. When a bubble/contact story establishes the political dynamics of the isolation decision, that becomes trunk history that the medical drama inherits.

The contribution flow is like sugar: it's what makes the root system grow. A shared universe with no active projects is a root system producing no sugar. It doesn't develop further. The creative work at the leaf level is what drives growth at every level of the tree.

The root system is co-constructed

This bidirectional flow has a practical implication: the shared universe canon isn't finished before the projects begin. It starts as a set of foundational commitments (the physics, the species existence, the structural principles) and grows as the projects feed it. Much of the richest shared-world canon gets generated at the project level first and then accepted into the root system.

In Transmission Zero, the detailed biology of each species wasn't established top-down. It emerged through storytelling. A medical case involving Species C required understanding their internal biochemistry, so their biochemistry was developed in that context and then recognized as root-level content that all projects would need to respect. A character interaction in the bubble/contact project required understanding Species D's three-channel communication system, so that system was developed and fed back into the roots.

The universe-level stewardship role, then, isn't just maintaining a static document. It's actively integrating contributions from the projects, checking them for cross-project consistency, and managing the growth of the root system over time. The root grows because the leaves feed it, but someone needs to make sure the incoming sugar doesn't poison the tree.

Temporal dependencies

The Transmission Zero tree has an additional wrinkle that many shared universes will share: its two branches are set in different eras. The bubble/contact project is set earlier in the timeline, so its events become history that the medical drama inherits. But the medical drama was developed first, which means it has already assumed things about that history.

The dependency runs in both directions. The earlier-era project constrains the later-era project's past. The later-era project constrains the earlier-era project's future. Both projects need to check against each other when establishing events that fall within the other's temporal scope.

This is a governance problem, not a creativity problem. The solution isn't to develop the projects in chronological order (which would mean the medical drama couldn't move forward until the bubble/contact stories were complete). The solution is to make the cross-project dependencies visible and to have a protocol for managing them.

The contribution protocol

The Transmission Zero constitution includes a specific protocol for how content moves from leaf to root:

Detection. When working in a project, notice when a creative decision touches root or trunk content. The test is simple: does this decision constrain what another project can do? If yes, it's contributing to the shared layers, not just the project branch.

Flagging. Mark the contribution in the project's reference document with a note identifying its tree position. "This story establishes that Species C's internal biochemistry uses silicone-bridged chains. Root-level content; cross-reference needed." The flag doesn't need to be resolved immediately. It needs to exist so that the next time any project touches that area, the dependency is visible.

Assessment. Check whether the contribution is consistent with existing root and trunk canon and with what the other project has established or assumed. For a solo author, this means checking the other project's reference document. For multiple contributors, this is where the steward earns their role.

Acceptance. If the contribution is consistent, it enters the root or trunk at the appropriate canonical level (usually working canon, hardening to established as other content builds on it). If it conflicts, the conflict needs resolution through the change process before the contribution is accepted.

Propagation. Once accepted into the root or trunk, the contribution is available to all projects and constrains all projects. Update the universe-level reference material.

Branch-to-branch independence

One of the tree model's clarifying virtues is that it defines what doesn't need coordination, not just what does.

Two projects on different branches don't directly constrain each other above their respective branch points. A medical drama story about the station's governance doesn't affect the bubble/contact project's setting, and vice versa. They interact only through the shared root and trunk. If both projects happen to be contributing to the same part of the root system (both establishing details about Species A's biology, say), those contributions need to be reconciled at the root level, not between the projects directly.

This means the coordination overhead doesn't scale with the number of projects. It scales with the density of root-level contributions. Two projects on distant branches might barely interact except through the root system. Two projects on the same branch need tight coordination. The branching pattern determines the coupling, which makes the governance cost predictable.

Why this matters for solo authors

This structure might sound like it's designed for large collaborative projects with multiple teams. But a solo novelist with two books set in the same world is already managing a tree, whether they know it or not.

The world shared between the books is the root system. The specific story of each book is a branch. Details established in one book that constrain the other are root-level contributions that have flowed from leaf to root and back. The author who discovers a contradiction between their two books has discovered a failure of root-level stewardship, not a creative problem.

The tree model helps because it makes the structure visible. Instead of vaguely knowing that the two books share a world, you can articulate exactly what's shared (the root system and whatever trunk they have in common) and what's independent (everything above their branch point). You can track which creative decisions in each book have propagated into the shared layers and need to be respected by the other. You can assess the impact of a proposed change by tracing it through the tree: does it touch the roots? The trunk? Just this branch?

The model also scales naturally. When a third project enters the Transmission Zero universe (and the constitution explicitly anticipates this), it plugs into the existing tree at whatever branch point makes sense. Everything below that point is inherited. Everything above it is the new project's own territory. The governance framework doesn't need to be redesigned; it just grows a new branch.

A shared universe isn't a hierarchy with a parent at the top, issuing constraints downward. It's a living system where constraint and contribution flow in opposite directions, where the creative work at the edges feeds the shared center, and where the center, in turn, makes the creative work at the edges possible. The tree model captures this reciprocity. Governance for a multi-project world needs to account for both directions of flow, not just the one that feels like control.