Back to inline

Agents are principals too

Permissions are a module and action statement resolved over platform, organization and repository scopes. People, agent keys and share links are all principals in the same model, so one model answers who can do what, and where.

Delegation that
cannot widen

An agent key carries its own scopes, intersected with its owner's permissions and re-resolved on every call and every repository. Handing work to an agent can only narrow what is reachable, not broaden it.

Rolesacme · 42 people, 3 agents
Owner
everything, including billing and platform
2
Admin
configure review, security, and connections
6
Member
their own pull requests and reviews
34
Agent · release-bot
reviews:read ∩ owner's permissions
2 repos

An agent's authority is its own scopes intersected with its owner's permissions, resolved per call and per repository.

Included

Route coverageevery route declares what it needs, and a test fails if one does not
Scoped rolesOwner, Admin and Member, plus grants at repository scope
Share linksa public walkthrough link is a principal with exactly one capability
Audit logwho did what, on which workspace, and when

Put it on one repository

Connect GitHub, enable a repo, and the next pull request opened gets a review.