Civilization Operating System
noos.iai.one is the standalone Civilization Operating System project in the iai.one ecosystem. It is the meta-architecture layer above Flow and App, covering system map, governance, standards, and long-horizon operating logic.
Role In The Ecosystem
Meta-Architecture
NOOS describes the higher-order system model instead of daily workflow authoring or operator execution.
Governance
It publishes standards, approvals, trust logic, rollback concepts, and strategic framing for the broader system.
Roadmap Layer
NOOS is where long-horizon structure and device or operating-model expansion should become explicit.
Published Route Structure
| Route | Purpose |
|---|---|
/ |
NOOS homepage and public entry. |
/docs/ |
NOOS docs hub. |
/docs/civilization-os/ |
Flagship Civilization OS page. |
/docs/system-map/ |
Operating layers and object model. |
/docs/device-matrix/ |
Mission-class BOM and hardware fabric planning. |
/docs/evidence-anchors/ |
Foundational standards and reference anchors. |
/docs/governance/ |
Approvals, trust, rollback, and evidence rules. |
/docs/roadmap/ |
Long-horizon roadmap and phase deliverables. |
/docs/api-contracts/ |
Early API contract documentation for the NOOS surface. |
Boundary With App And Flow
NOOS Does
- Define the meta-model that frames product layers.
- Own governance, standards, and system-map semantics.
- Describe the operating logic above individual workflows.
NOOS Does Not
- Replace Flow as the builder and execution surface.
- Replace App as the operator workspace.
- Serve as the primary delivery UI for everyday users.
Observed Live Note
In the March 28, 2026 live snapshot, the NOOS page content is reachable, but the HTML title still appears to carry older Muon Noi investor-shell branding. The NOOS team should align live metadata with the intended Civilization OS positioning.