The roadmap

Three phases,each complete on its ownterms.

Each phase ships a complete product, not a waypoint that only works when finished. Phase 1 is the realm. Phase 2 deepens it. Phase 3 makes it native.

01NOW0203040506
Phase 1
Foundation
Phase 2
Enterprise depth
Phase 3
Native substrate
Current
Phase 1 in build

A roadmap that says yes to everything is not a roadmap. Each phase has a definition of “done,” and each definition requires the entire phase, not most of it.

Phase 01

Foundation

In build now · the first complete product
PHASE 01 · FOUNDATIONFOUNDATION TIERSigilWitnessAPPLICATION TIERSynodNexaVigilCharterCommonsArbiterRetinueSDK · WALLET · SCAN
Phase 1 complete when

All nine components in production. Public mainnet running with a real validator cohort. SDK, Wallet, and Scan usable by external builders. Federation v1 supports inter-system access. The realm is operationally a place, not a project.

01
Now

Foundation in build

  • Architecture lock complete
  • Sigil and Witness in active build
  • Substrate decision committed
02

Application tier build

  • Synod, Vigil, and Commons move design → build
  • Foundation tier reaches first internal release
  • SDK takes its earliest usable shape
03

SDK alpha and lifecycle

  • Nexa and Charter advance to working build
  • SDK reaches alpha for early-access builders
  • Wallet and Scan take first integrated form
04

Public testnet

  • SDK beta; public testnet live
  • First full component set on testnet
  • Partner pilots begin; Charter v1 utility tokens validating
05

Phase 1 mainnet

  • Mainnet launch; all nine components in production
  • Public SDK release
  • Federation v1 online
06

Stabilization

  • Mainnet stabilization; validator cohort expansion
  • Phase 2 component foundations enter design
  • Phase 1 reaches steady-state operation
Phase 02

Enterprise depth

Follows Phase 1 · enterprise depth

Enterprise compliance

KYC/AML-compatible Sigil tiers. Regulatory reporting hooks. Institutional-grade onboarding with compliance-level attestation.

Digital twins

On-chain representations of physical systems. Real-world asset state tracked through Witness. Physical infrastructure participates in the realm.

Charter v2

Full tokenization model: regulated securities where jurisdiction permits, utility tokens with lifecycle management, and fractional asset infrastructure.

Marketplace primitives

Charter-based marketplace support. Xyress does not run a marketplace. These are the primitives that marketplace operators build on top of.

Phase 03

Native substrate

Long horizon · native substrate

Native substrate

The chain Xyress was always designed for. Custom cryptographic primitives, AI-native consensus operations, and governance designed from first principles.

AI in consensus

AI participates in consensus operations under bounded authority. Behavior attributed, ranked, and governed, consistent with how every AI actor in the realm works.

Full co-equality

Phase 1 is co-equal at the product surface. Phase 3 is co-equal in the substrate itself, the moment where the architectural commitment becomes the chain.

Long horizon

Phase 3 is deliberately positioned at the long horizon. What it will look like in detail depends on what Phase 1 and Phase 2 teach. The direction is fixed; the precise form is not.

What’s not on this roadmap.

01

A Xyress-operated marketplace for Charter-issued tokens.

02

A foundation-model training operation or competing AI research track.

03

An enterprise infrastructure product that abandons the realm architecture for faster enterprise adoption.

04

A governance token or speculative instrument before the platform has proven its utility.

05

Pivots to adjacent categories that would dilute the identity, trust, and AI co-equality thesis.