IAI System Map
The docs surface is only complete when the ecosystem boundaries are explicit. Each product surface must know what it owns and which neighboring surface it links to.
System Map
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.
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.
Pages To Keep In Sync
- home.iai.one: primary vision page should link to docs overview, architecture, and ecosystem map.
- app.iai.one: operator shell should link to docs for API, security, and mail/system alert behavior.
- flow.iai.one: builder UI should link to getting started, flow docs, deployment, and API reference.
- 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.
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.
Support Surface
Error states, empty states, and operator actions should point back into docs pages instead of leaving users stuck.