Understanding product status
NomOS states how mature a feature is wherever it appears: at the feature, in the roadmap, and in the architecture. These words always mean the same thing. You never need the changelog to understand a status.
Find settings
Section titled “Find settings”Platform settings are grouped by topic. “Search settings” finds these destinations only; the header search finds workspace content. Open “Show categories” to select one or more topics. The number shows your active selection even when collapsed. Search and selection apply together; collapsing does not clear filters. “Reset filters” restores every entry. Detailed guidance remains on each settings page and its help. Filters do not change permissions.
Email delivery provides settings for direct provider APIs. An available settings page does not mean that sending is configured or delivery verified. SMTP remains a deployment setting and has no dialog of its own.
Find settings
The four words at the feature
Section titled “The four words at the feature”These words sit directly at the feature, on tiles, in badges, and in tables:
Available
Shipped and usable in the product. Everything the release history names is available.
Experimental
Shipped but deliberately marked as a trial: behaviour and limits may still change. Examples: the C0 data class and models that process outside the EU/CH area.
Planned
Decided but not shipped yet. A planned feature is deliberately inactive; it is not broken and needs no report. The roadmap shows which features are planned.
Target
A date in the roadmap. Targets are not promises: an elapsed target date says nothing about quality, only that the date has passed. The status beside it stays decisive.
Status in the roadmap
Section titled “Status in the roadmap”Every roadmap item carries one of three statuses (BDR-023):
Committed
The scope rests on a carried decision; it will be built.
Candidate
Plausible and prioritised, but not yet bindingly decided.
Exploration
Being explored to learn whether and how it makes sense. A date beside it says when we aim to know more, and not when it ships.
Only what the release history lists is shipped. The roadmap shows direction, not delivery state.
The architecture is a model
Section titled “The architecture is a model”The logical architecture describes, as a model, how NomOS handles governed requests. It shows neither the live state of a concrete deployment nor production endpoints or topologies.
What actually ran is evidenced by the audit log; what is shipped is in the release history.