This document covers each part of that flow — what roles are, what positions are, what titles are, and how they connect.
A role is a named set of accountabilities held by a person within a circle in Wild OS. Roles define what you are responsible for — specific outcomes, decisions, and areas of ownership. A person holds multiple roles, across one or more circles. Roles are defined in governance and live in the Roles database.
A role is not a job description. It's a clear statement of what you own — and what you're expected to deliver.
A position is the internal label that describes the scope of your work — broad enough to map to a Ravio benchmark, specific enough to reflect meaningful differences between people.
Positions are defined after roles. Once the roles someone holds are clear, you can ask: what is the overall scope of this person's work? That scope becomes their position.
If two people have genuinely different scopes of work, the answer isn't different titles — it's different positions. Positions capture real differences in responsibility. Titles don't.
A position is not a job title. It's the internal description of scope that flows through to compensation.
A title is the external expression of your position and level. It's what you put on LinkedIn, use in your email signature, and share with the outside world.
Titles matter — they're motivating, they're a recognition of someone's work, and they carry meaning externally. But they're the output of the flow, not the input.
Titles follow positions and levels. They don't drive them.