IAI Documentation
The Infrastructure for AI Workflows, Communication, and Civilization Systems
What Is IAI
IAI is a connected system of charter surfaces, workflow execution, communication delivery, operator control, developer interfaces, control layers, and core infrastructure. This docs site is the single place to understand how those surfaces fit together.
Charter + Entry
iai.one and home.iai.one define the constitutional root and the portal entry into the system.
AI Workflow Engine
flow.iai.one provides the visual builder, node graph, execution runtime, and automation layer.
Communication Layer
mail.iai.one handles transactional email, notifications, and system alerts coming out of flows and services.
Operator + Control Surfaces
app.iai.one, dash.iai.one, noos.iai.one, and cios.iai.one cover operator control, dashboards, and higher-order control layers.
System Overview
The runtime path is designed to be simple to understand for new users and explicit enough for developers to deploy quickly.
Quick Links
Getting Started
Understand the system and run your first flow in minutes.
Build Your First Flow
Node types, JSON shape, execution lifecycle, and builder behavior.
Send Your First Mail
Use the communication layer for transactional messages and alerts.
Operator App
See how app.iai.one fits as the control surface for review and operations.
Dashboard Surface
Clarify the role of dash.iai.one, dashboard routing, and analytics ownership.
Developer Portal
Understand how developer.iai.one should own integrations, SDKs, and webhooks.
API Docs
Base URL, auth model, endpoint groups, and response contracts.
Security Model
Strict CSP, no analytics, no external scripts, Cloudflare-native stack.
iai.one
Understand the charter root and what the public constitutional surface should own.
home.iai.one
See how the portal should route visitors into products, docs, and developer surfaces.
NOOS
Read the Civilization Operating System layer, governance, and strategic map.
CIOS
See how the control-layer shell and backend foundation fit into the system.
Ecosystem Map
See how home, app, flow, mail, docs, and API surfaces connect.
Service Registry
Audit the full domain map, stack ownership, live status, and unresolved DNS surfaces.
Owner Checklist
Give every DEV team a shared checklist for help links, routing notes, and canonical docs.
Observed Domain Status
The docs now track the live status of each listed domain. At this snapshot, cdn.iai.one and flows.iai.one do not resolve publicly, and api.flow.iai.one is reachable but returns a 404 JSON response at root.
Open the full service registry to review every surface, stack, and ownership boundary in one place.
Designed For Every Stakeholder
New Users
Understand the overall system fast enough to start exploring flows and outputs.
Developers
Move from architecture understanding to local setup and deployment with clear commands.
Founders & Investors
Read the platform shape, scope, product boundaries, and next capability layers.
Documentation Map
Core Reading Path
- Start with Getting Started.
- Use iai.one and home.iai.one to align the public root and the portal layer.
- Use Service Registry to orient around the full iai.one domain map.
- Move to Architecture for the four-layer model.
- Use Flow and Mail to understand execution and communication behavior.
- Use Owner Checklist before rollout so each team knows what help/docs they must keep current.
- Finish with Deployment and Security before production rollout.
This site uses only first-party static assets. Search is local, code copy is first-party JavaScript, and the Cloudflare Pages output can stay fully self-hosted.