Deployment Scope

This page explains how to read deployment support in the current docs. The repository architecture is broader than the currently release-blocking path, so deployment claims must be interpreted through current supported scope rather than through roadmap ambition alone.

Current Scope

The current product and repository materials indicate that Phase 1 narrows to one primary end-to-end path before broader chain expansion. That means deployment support should be read as a constrained current lane plus a modular multi-chain roadmap, not as universal parity across every listed chain.

Future Direction

Broader chain adapters remain part of the architecture direction and longer-term platform design. They should be added to the public truth set only after the narrower MVP lane is stable, observable, and proven against the release criteria used in the control plane and hardening roadmap.