Routing
Routing
The direction of travel, tracked in the open.
The roadmap describes the trajectory of the system after Genesis: the expansion of supported networks and bridges, the growth of the validator set through successive cohorts, and the broadening of the corridors the system can serve. Each of these follows the standards established at activation — depth, reliability, and auditability — rather than relaxing them to move faster.
The roadmap lives in the repository as ROADMAP.md and is versioned alongside the code, so integrators and observers can see direction and sequence in the open. It is directional rather than a calendar of hard dates: it communicates intent while leaving room for the criteria above to govern the actual pace.
After Genesis the principal improvements are expansion (more networks, more bridges, deeper aggregated liquidity), refinement (better routing inputs and scoring), and hardening (a maturing validator set and security model). Expansion increases the system's reach; refinement increases the quality of each route; hardening increases the trustworthiness of each settlement.
Where specific roadmap items depend on post-Genesis decisions, they are described as direction rather than commitment. The roadmap is kept current as phases complete, through changesets reviewed in public.