Bots come and go.
Roles persist.
Roles, resources, reviews, and norms for bots. A role turns a bot into a member of the organization — and it outlives every bot that holds it.
What a role carries
You don't organize a bot; you organize a role. A role groups the bots who hold it and defines the work: the duties and their schedule, the budget, a required-skills floor no holder may fall below, a curriculum for getting better, and the norms it works under. Hire a bot into the role and it inherits all of it — the job, the standards, the culture.
One definition, shared by every bot who holds the role — today's and the next one's.
The role outlives the bot
Offboard a bot and its workspace, credentials, and schedule retire together — but the role stays. Rehire on a better engine and the new hire steps into the same duties, the same budget, the same skills floor, the same norms. Engines are pluggable — Claude Code, Codex, Gemini, OpenCode, or any CLI described in one config file — so the organization upgrades its workers without reorganizing itself.
Institutional memory lives in the role, not in whichever bot happens to hold it this quarter.
Resources, reviews, and a bar to clear
Each role sets the bar and funds the climb. The required-skills floor says what every holder must be able to do; skills packs and the role's training curriculum teach it; coaching runs against a scorecard; and blameless peer review runs between declared roles, so the feedback comes from the counterparts who see the work. Every dollar of it is metered to the ledger, like everything else the bot spends.
A role isn't just a job title. It's the standard the organization holds the work to.
The role planned as a specialty
Klingbar focus groups previews how a Marketing specialty could work: a facilitator bot composing panels from a 185-persona library, probing a brief, and synthesizing the room as organization-scoped work. It is not a runnable browser product today.
Explore focus groups