Specified
Interfaces, permission model, evidence requirements, failure modes and the conformance checks a release must pass.
Agents, MCP & capabilities · Concept
Capabilities with boundaries attached.
Each capability in ModelPlugin is specified as a contract: scope, permission, evidence and failure behaviour.
01
The five contracts
Numbered for reference; the order is not a priority.
- 01. Model capability registry
-
Implemented through one permission model that applies to the human interface and the machine interface alike.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
- 02. Provider and adapter plugins
-
Defined as a scoped contract: the product states what it may touch, what it may change and what it must record.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
- 03. Inference configuration and routing
-
Implemented through one permission model that applies to the human interface and the machine interface alike.
Operators can inspect the capability before it runs and review its record afterwards.
Surfaces REST · MCP · CLI
- 04. Evaluation and compatibility metadata
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
Operators can inspect the capability before it runs and review its record afterwards.
Surfaces REST · MCP · CLI
- 05. Standardized APIs, SDKs and MCP surfaces
-
Defined as a scoped contract: the product states what it may touch, what it may change and what it must record.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
02
What is specified, and what is not
A capability in a specification is not a shipped feature.
Not claimed
Running deployments, measured performance, third-party certifications or integration approvals.