Audience 01
Developers
Adopts it to replace a patchwork of tools with one reviewable surface.
Agents, MCP & capabilities · Concept
Where the work actually changes.
PluginRegistry is aimed at Developers, enterprises, platform providers, software publishers.
01
Who it is for
Three audiences, one boundary model.
Audience 02
enterprises
Uses the product where the cost of an unscoped action is higher than the cost of setup.
Audience 03
platform providers
Adopts it to replace a patchwork of tools with one reviewable surface.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Canonical capability manifests | Removes an ad hoc step from the workflow. | Specified |
| Identity and provenance verification | Removes an ad hoc step from the workflow. | Specified |
| Compatibility and conformance testing | Removes an ad hoc step from the workflow. | Specified |
| Searchable registry APIs | Removes an ad hoc step from the workflow. | Specified |
| Versioning, revocation and lifecycle governance | Turns a manual control into an explicit contract. | 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.