Genesis

Arc Route activates in defined phases, collectively the Genesis sequence. The phases exist to bring the system online in a controlled order: the open-source protocol and documentation first, then the components required for live execution, then the settlement and validator infrastructure required for finality. Settled transfers are gated behind the appropriate phase and are not active beforehand.

This phasing is not a countdown to be rushed through; it is the sequence in which the system's guarantees are established. Each phase has criteria the next depends on, and no phase is shortened by skipping its predecessor.

At present the system is pre-Genesis. The repository, the documentation, the interfaces, and the design described in these pages are observable, but the components that move and settle value are not yet active for end users. This is stated plainly so that nothing here is mistaken for a live, settled capability.

Pre-Genesis also has a protective purpose: it prevents premature engagement with the system before its security and settlement guarantees are in place. The Genesis timeline communicates when that changes.