Knowledge · Help
Roles
Roles bring a person's characteristics and subject orientation into the usage context. Here you learn how roles influence relevance, weighting, and the preparation of knowledge.
After this page, you can
- understand roles as usage context in the knowledge graph
- distinguish context relevance from weighting
- explain how a role influences navigation and perspectives
What a role describes in Nexonoma
A role is a context node for a person's characteristics, direction of responsibility, and subject orientation in a specific situation. It connects usage context with the knowledge graph and helps Nexonoma select suitable content and perspectives.
- A role describes a person's subject point of view in a situation.
- It includes focus, direction of responsibility, decision scope, information needs, and priorities.
- The same person can take on several roles depending on the task.
- Examples include Software Architect, Reviewer, Engineering Lead, and Product Manager.
Role model
The role connects person, situation, and knowledge
The subject point of view controls which content matters to the current task and which of it receives priority.
Role
characteristics and orientation
Person
takes on the role
Task
sets the goal
Relevance
selects suitable knowledge
Weighting
orders priorities
Perspective
prepares knowledge
Context relevance: which knowledge matters?
Context relevance describes which content building blocks matter to a role in a concrete situation. It connects the task, subject point of view, and available knowledge into a suitable selection.
- For a technology decision, a Software Architect primarily needs architectural effects, dependencies, and operational consequences.
- An Engineering Lead additionally considers team capability, delivery flow, and organizational risks.
- A Reviewer focuses more strongly on assessment criteria, evidence, and visible weaknesses.
- The role therefore helps select the relevant subject nodes from many possible ones.
Weighting: what receives priority?
Weighting orders selected content by its importance to the role and current task. It controls which aspects are presented first, in more depth, or with greater prominence.
- High weighting brings a building block or aspect to the foreground.
- Medium weighting keeps supporting knowledge easy to reach.
- Low weighting preserves subject context without overloading the current workflow.
- Weighting can change when the task, situation, or role changes.
How roles work in Nexonoma
Roles add usage context to the stable subject knowledge core. Catalog and graph keep their stable content while navigation and perspectives can create a role-appropriate selection and reading direction.
- Navigate uses the role as a signal for a suitable entry point.
- Perspectives can prioritize examples, criteria, and risks for the role.
- Learning paths can account for prior knowledge, responsibility, and learning goals.
- Decision and risk views can highlight the effects most important to the role.