High-Level Architecture
Six layers, one direction of flow: from a human, through knowledge and AI, out to readers.
ichi is a pipeline of trust. Signal and work flow down; only proposals flow back up. Nothing crosses the human gate without approval.
flowchart TD
H["Human — intent + final approval"] --> K["Knowledge — the vault / memory"]
K --> OS["AI Operating System — agents that gather, connect, monitor, draft"]
OS --> EO["Executive Office — a virtual C-suite that reviews"]
EO --> P["Products — what the system ships"]
P --> R["Readers — receive only finished, approved work"]
The layers
| Layer | Role |
|---|---|
| Human | The origin and the final gate. Sets intent; approves or rejects output. |
| Knowledge | A single vault of notes, logs, and drafts. The system’s memory (Chapter 04). |
| AI Operating System | Agents that gather signals, connect ideas, monitor health, and draft. |
| Executive Office | A virtual C-suite that reviews the same work from many angles (Chapter 03). |
| Products | ichiOS, IAS Brain, WkndPrjct (Chapter 05). |
| Readers | The public. They see only the finished, human-approved result. |
Why one direction
The arrows are one-way for action. An agent can draft an essay, flag an anomaly, or propose a decision — but it cannot publish, spend, or ship. Those actions return to the human gate first.
This is the single most important design choice in ichi, and it is not a technical one. It is a governance one: automation earns trust by being reversible and gated, not by being autonomous.