Audience 01
Agent developers
Needs the same permission model for people and agents.
Agents, MCP & capabilities · Concept
Where the work actually changes.
AgentPlugin is aimed at Agent developers, software vendors, enterprise builders, capability publishers.
01
Who it is for
Three audiences, one boundary model.
Audience 02
software vendors
Needs the same permission model for people and agents.
Audience 03
enterprise builders
Uses the product where the cost of an unscoped action is higher than the cost of setup.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Agent and capability manifests | Turns a manual control into an explicit contract. | Specified |
| Dependency and version management | Makes an existing action reviewable. | Specified |
| Signed distributable packages | Makes an existing action reviewable. | Specified |
| Sandboxing and installation workflows | Removes an ad hoc step from the workflow. | Specified |
| Licensing, telemetry and lifecycle tools | Removes an ad hoc step from the workflow. | Specified |
03
Migration
How a team would move from the status quo without a big-bang cutover.
Step 01
Map the current path
Name the tools, owners and handoffs that the product replaces. Nothing is removed yet.
Step 02
Run one capability
Pick a single scoped capability and run it alongside the old path, with evidence compared side by side.
Step 03
Retire the old path
Remove the previous tool only when the new record is complete enough to audit.