Connectivity Foundation
The connection layer is presented publicly as one owned experience, not a collection of carrier fragments.
Public framing
The public website should communicate a simple idea:
one connection surface, one clear next step, one place to stay oriented
That means the web surface should avoid:
- provider leakage
- telecom-admin phrasing
- fragmented route language
What the homepage is signaling
The homepage sequence introduces connectivity as:
- global in reach
- local in execution
- calm in presentation
- connected to the rest of the Onyx stack
What this docs layer is for
The docs layer is not a second marketing site.
It exists to let Onyx publish:
- technical documentation
- public architecture context where appropriate
- implementation notes that should be versioned and reviewable
Later docs passes can expand into richer product-specific surfaces, but the foundation stays repo-owned and explicit.