IAI System Map
The docs surface is only complete when the ecosystem boundaries are explicit. Each domain must know what it owns, what it publishes, which layer it belongs to, and whether the live route already matches the intended system map.
System Map
iai.one
Wix charter root and constitutional entry for the ecosystem.
home.iai.one
Vision, positioning, and the core infrastructure narrative.
app.iai.one
Operator workspace, review surface, and human-facing control layer.
flow.iai.one
Workflow builder, execution engine, and node system.
dash.iai.one
Dashboard shell and redirect entry into dashboard-specific routes.
developer.iai.one
Developer portal for APIs, SDKs, node development, and technical onboarding.
api.flow.iai.one
Dedicated Flow Engine API worker surface for route-based engine operations.
nft.iai.one
Public NFT registry, metadata surface, and crypto asset disclosure layer.
noos.iai.one
Civilization OS meta-architecture, governance, and system-map layer.
cios.iai.one
Customer Intelligence OS control-layer surface and backend foundation.
mail.iai.one
Communication layer for transactional delivery and notifications.
api.iai.one
Gateway and platform contract surface.
docs.iai.one
The knowledge hub explaining how the rest of the system fits together.
cdn.iai.one
Planned Cloudflare CDN surface. DNS was unresolved in the March 28, 2026 snapshot.
flows.iai.one
Planned n8n automation surface. DNS was unresolved in the March 28, 2026 snapshot.
Domain Registry Snapshot
api.flow.iai.one is reachable but returns 404 JSON at root, while cdn.iai.one and flows.iai.one do not currently resolve in DNS.
| Domain | Layer | Observed State | Primary Documentation Need |
|---|---|---|---|
iai.one |
Charter | 301 → www.iai.one then 200 |
Public constitutional framing and root-domain policy. |
home.iai.one |
Portal | 200 HTML | Entry-path map and system narrative. |
app.iai.one |
Product | 302 → www.app.iai.one then 200 |
Explain apex vs V2 web-app routing and operator ownership. |
flow.iai.one |
Product | 200 HTML | Builder, runtime, execution, and node-system docs. |
dash.iai.one |
Product | 200 HTML shell | Dashboard entry and dashboard route ownership. |
developer.iai.one |
Developer | 200 HTML | SDK, auth, webhook, and node-development references. |
api.iai.one |
API | 200 JSON | Platform route groups and auth/current contract documentation. |
api.flow.iai.one |
API | 404 JSON at root | Route-level engine contract docs rather than homepage-style docs. |
noos.iai.one |
Strategy | 200 HTML | Meta-architecture, governance, and operating-model docs. |
cios.iai.one |
Control Layer | 200 HTML | Customer Intelligence OS shell + backend foundation split. |
mail.iai.one |
Delivery | 200 HTML | Mail UI, API, and server-ops boundary documentation. |
cdn.iai.one |
Infra | DNS unresolved | Publish only after DNS and public endpoint are live. |
flows.iai.one |
Automation | DNS unresolved | Publish only after public n8n routing and auth model are live. |
Open the full service registry for stack and notes across each domain.
Pages To Keep In Sync
- iai.one: charter root should link to iai.one docs, the portal docs, and the ecosystem map.
- home.iai.one: primary vision page should link to docs overview, architecture, and the home.iai.one explainer.
- app.iai.one: operator shell should link to the App Surface docs plus API, security, and mail or system-alert behavior.
- flow.iai.one: builder UI should link to getting started, flow docs, deployment, and API reference.
- dash.iai.one: dashboard entry should explain what lives at apex versus
/dashboard/. Use the Dashboard Surface page as the canonical explainer. - developer.iai.one: developer portal should either become the canonical API or onboarding source or explicitly defer to the Developer Portal docs.
- nft.iai.one: public registry should link to disclosure policy, metadata schema, and verification rules.
- noos.iai.one: governance and meta-architecture should link back to ecosystem and the NOOS docs.
- cios.iai.one: control-layer shell should explain its relation to NOOS, Flow, and its backend or API foundation through the CIOS docs page.
- mail.iai.one: mail surface should link to mail docs, API, security, and system alert flows.
- api.iai.one: developer surface should link back to architecture, SDK, and deployment docs.
- cdn.iai.one: keep the CDN page marked as planned until DNS is live.
- flows.iai.one: keep the automation page marked as planned until public routing and auth are live.
Help + Docs Completion Checklist
Cross-linking
Every product header or footer should expose a docs entry and at least one directly relevant reference page.
Shared Vocabulary
Flow, node, execution, output, operator, alert, and runtime should mean the same thing everywhere.
Status Clarity
Current MVP vs future capability must be visible on home, app, flow, and mail surfaces.
Routing Clarity
Apex domains, www redirects, and route-only worker surfaces must be documented explicitly so operators do not guess the wrong entrypoint.
Proof Surfaces
NFT and treasury disclosures should publish proof states explicitly instead of implying assets or mint readiness.
Support Surface
Error states, empty states, and operator actions should point back into docs pages instead of leaving users stuck.