The OS family
Modules
A module is a go-to-market function running on the shared layers. ContentOS is the first OS on the brain.
Semi-manual
What a module is
The layers are shared: the store, the gate, the trackers, the measurement. A module is one go-to-market function running on top of them — the agents, the triggers and the review standards for that particular kind of work.
ContentOS is the content function. A sales function or a retention function would be a different module reading the same store.
Why this shape matters commercially
A second module is cheap in a way a second product is not, because it reuses the layers rather than rebuilding them. The keyword tracker that serves content serves sales unchanged; so does the store, and so does the gate.
That is the whole argument for building this way round — state first, functions second — rather than shipping a content tool and retrofitting a store underneath it later.
What exists
One module. ContentOS is the first OS on the brain, and it is the only one being built. Naming the family is not a promise that another is coming, and no date attaches to anything beyond the first.