Owner Checklist
Every public surface in the ecosystem needs an owner, a documentation boundary, and a release-time checklist. This page is the shared contract for teams maintaining help and docs across iai.one.
Minimum Docs Kit For Every Surface
- Purpose: what the surface exists to do.
- Boundary: what it owns and what it does not own.
- Entry route: apex,
www, redirect, or route-only API. - Auth model and support path if the surface is operational or developer-facing.
- Links back to relevant pages on
docs.iai.one.
Surface Matrix
| Surface | Owner Focus | Must Document | Must Link |
|---|---|---|---|
iai.one |
Charter team | Constitutional role, public narrative, next-step routing. | iai.one docs, portal docs, registry |
home.iai.one |
Portal team | Entry routes, product map, audience routing. | home docs, getting started, ecosystem |
app.iai.one |
Operator app team | Workspace modes, review flows, operator actions. | app docs, API, mail |
flow.iai.one |
Builder team | Node system, execution model, runtime logs, walkthrough. | flow docs, deployment, API |
dash.iai.one |
Dashboard team | Apex vs /dashboard/, dashboard modules, metrics sources. |
dash docs, API |
developer.iai.one |
Developer platform team | Auth, SDKs, webhooks, node or extension authoring. | developer docs, API, SDK |
mail.iai.one |
Mail ops team | Mail UI boundary, send API, alert ownership, admin path. | mail docs, security |
api.iai.one |
Platform API team | Current route groups, auth, response shapes, change policy. | API, developer |
api.flow.iai.one |
Flow engine team | Route-level contracts, error envelopes, engine auth. | API, flow docs |
noos.iai.one |
NOOS team | Governance, meta-architecture, route map, branding consistency. | NOOS, ecosystem |
cios.iai.one |
CIOS team | Shell vs backend split, health routes, deployment boundary. | CIOS, NOOS |
cdn.iai.one |
Infra team | DNS, cache policy, asset path taxonomy, versioning. | cdn docs, security |
flows.iai.one |
Automation team | n8n boundary, auth, webhook policy, incident model. | flows docs, flow docs |
Release-Time Checks
- If a public route changes, update docs the same day.
- If auth or onboarding changes, update both the user-facing explainer and the technical guide.
- If a hostname is not publicly live, mark it as planned instead of implying availability.
- If help links are added to a product surface, they must point to the canonical page on
docs.iai.one.