Rooms and data classes
A room is the unit in which NomOS manages knowledge, rules, and decisions. Rooms form a tree: organisation, department, team, project.
What a room defines
Section titled “What a room defines”- Owner. The person responsible for the room’s content and rules.
- Data class. A protection level from C0 (public) to C3 (strictly confidential). Among other things, it decides which models may process the room’s content.
- Members and roles. Only members see a room’s content. NomOS checks access before every query, regardless of the model.
- Brains. Every room has its own brain with its knowledge. A room can also subscribe to brains from the catalogue, such as a reference library. Subscribed knowledge informs answers. When a subscription is marked binding, NomOS retrieves its sources first and presents them to the model as authoritative. Answers are not technically checked against them.
Inheritance
Section titled “Inheritance”Rules apply in the room where they are set and in every room below it. A project room therefore inherits the rules of its team, its department, and the organisation. Access to knowledge is not inherited: a member of a project does not automatically see the department’s content.
Sources
Section titled “Sources”Knowledge comes from documents (Markdown and PDF), from decisions, and from reviewed proposals. Every entry carries an owner and a validity date. An import does not keep syncing with the source system; it takes the state at the time of import.