Future directions

This section collects forward-looking architecture explorations — designs for capabilities plexsphere does not have yet. Each page states a problem, weighs the options, recommends a shape, and names the decisions that would need sign-off before any code is written. The pages read as proposals, not as descriptions of shipped behaviour.

What is in this section

Self-contained design documents, one per topic. Each is a complete argument on its own: the problem, the alternatives considered, a recommended direction, and a phased delivery plan with its test and documentation obligations named up front.

When do I need it

Reach for these when you are evaluating a strategic direction, or preparing to turn one into tracked work — not when you need to operate or integrate against the system as it exists today. For what is actually built, stay in the bounded contexts and the reference. This section is kept separate from both on purpose, so a reader never mistakes a proposal for a contract.

Where is the entry point

• Federated relay fabric — a provider-operated relay tier beneath WireGuard that evolves today's bridge relay-fallback into a steerable reachability plane, plus a federation layer that lets two independent plexsphere instances interconnect across it.