Standardize the “who” primitive across your engineering platform.
Give agents, CI pipelines, internal tools, and workflow systems one consistent way to resolve who owns, approves, reviews, or handles work.
Roster replaces fragmented ownership logic with a shared participant-resolution layer available through MCP, REST, CLI, and web.
One primitive. Four surfaces. Every consumer.
resolve() is the shared platform capability. Every engineering surface — agents, pipelines, internal tools, workflow engines — calls the same function through whichever transport already fits its context.
Ownership is scattered across the engineering stack
Platform teams inherit organizational logic spread across half a dozen systems. Each is useful for something. None answers every runtime question about who should act.
Roster gives the platform a reusable resolution service rather than another static ownership screen — one that answers who should act for this project, this responsibility, and this moment.
Example: production release approval
A deployment pipeline is ready to promote Atlas to production. Instead of hard-coding a reviewer list in YAML, it calls the Roster CLI:
Complement your existing ownership systems
Roster doesn't replace your software catalog, CODEOWNERS, Git provider, incident platform, identity provider, workflow engine, or internal developer portal. Those systems can stay sources — or destinations.
Designed for platform control
Roster runs where your engineering systems already run and stays under platform-team governance end-to-end.
What platform teams can standardize
Every one of these resolution questions gets the same answer, whichever surface asks — and the same audit trail.