CIOS

Customer Intelligence OS

cios.iai.one is the Customer Intelligence OS layer. In the current ecosystem it combines a public control-layer shell with a separate backend or API foundation rather than existing as a Pages-only marketing site.

Two-Part Structure

Static Shell

The repository ships a responsive Pages-delivered shell under site/. It is intended for mobile-style navigation, PWA behavior, and future wrapper compatibility.

Backend Foundation

The same repository also contains the API or backend layer, versioned under semver and designed to run as a Node process outside Cloudflare Pages.

Backend Notes

Versioning

Public REST routes are namespaced under /v1, with future breaking changes expected to move to /v2.

Discovery

GET /v1/meta is intended to expose version, compatibility, and capability flags for clients.

Health

GET /health and GET /health/db define the minimum operational checks for the backend layer.

Position In The Broader System

With NOOS

NOOS defines the higher-order meta-architecture. CIOS is the more operational control-layer implementation beneath that strategy layer.

With Flow

Flow owns builder and execution semantics. CIOS should consume intelligence and state, not duplicate the workflow authoring model.

With App

App is the general operator workspace. CIOS should clarify which workflows, analytics, or controls are specialized enough to live outside the app surface.

What The CIOS Team Should Publish Next

Decide whether cios.iai.one documents the static shell, the backend API, or both with a visible split.
Publish the actual route map for the public shell and the deployment host for the backend API.
Document auth or session behavior for the backend process separately from Pages hosting.
State how CIOS differs from Dashboard and App to avoid overlapping product language.
Add screenshots if the shell becomes a real operator-facing UI rather than a concept surface.