Organization Roles govern the Organization
Every Membership has one fixed Organization Role: Owner, Admin, or Member. Owner is the unique recovery authority; Admin handles normal administration without Owner recovery powers; Member may create Agents and use shared Templates and Skills but cannot manage shared definitions. These roles do not grant Member authority over every Agent.
Agent Access Roles govern one Agent
The locked Agent Viewer role grants Agent metadata, activity, logs, and cost reads. Editor adds configuration, lifecycle, Skill, and credential management. Owner adds deletion and access management. Organization Owner/Admin have implicit Agent Owner authority over Agents in their Organization.
Explicit and General Access are additive
Explicit Agent Access assigns one accepted Membership one role on one Agent. Agent General Access can dynamically grant one role to all current and future accepted Members. Their Permission sets are unioned; removing either source leaves authority from the other intact. New Agents default General Access to Restricted.
Visibility and response semantics
Repository queries must constrain inaccessible Agents and subordinate conversations, tool calls, costs, logs, Skills, configuration, and credential metadata before ordering, counting, or pagination. Return 404 for absent, cross-Organization, or invisible resources; 403 for a visible resource where the requested action is not permitted.
Historical decisions
The earlier assigned-access and permission-backed-Organization-role ADRs were superseded when Agent Access Roles became their own role family. Do not reintroduce role-name checks, binary assignment flags, or authorization grants embedded in tokens.