The architecture
A shared brain, a team of specialized agents, a human on the gate, and a loop that learns.
Six layers, shared
A layer is used by everything running on top of it. That is the test that separates one from a module: a keyword tracker serves content and sales alike, so it belongs here rather than inside either.
- The brain
- State. What the company has decided, with a record of how confident it is in each thing and who decided it.
- Built
- Signal
- Perception — what changed out there. Deliberately not in the first version.
- Not in v0
- The gate
- A person, before anything publishes. The edit is classified and written back.
- Built
- The loop
- Measurement, written back into the store so the next draft reads it.
- Roadmap
- RevOps
- Actuation — work written back into the systems the data came from.
- Not built
- Pipelines
- Four operations applied across every kind of content, never categories themselves.
- Semi-manual
Three of the six are not built. Stating that here is cheaper than having you discover it in a demo, and the two that are built are the two the rest depend on. The orchestrator — which play runs, on what trigger — is semi-manual and folded into pipelines rather than given its own page, because there is not yet enough to say about it.
Modules run on top
A module is a go-to-market function running on the shared layers. ContentOS is the first OS on the brain. A second one would reuse the same store, the same gate and the same trackers rather than rebuilding them, which is the entire argument for building it this way round.