Workspace & infrastructure · Concept

Capabilities with boundaries attached.

Each capability in LocalModels is specified as a contract: scope, permission, evidence and failure behaviour.

Status Concept Category Workspace & infrastructure Surfaces REST · MCP · CLI Contact info@localmodels.io

The five contracts

Numbered for reference; the order is not a priority.

01. Model catalog and compatibility discovery

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. Quantization and device-aware deployment

Defined as a scoped contract: the product states what it may touch, what it may change and what it must record.

Operators can inspect the capability before it runs and review its record afterwards.

Surfaces REST · MCP · CLI

03. Inference endpoint management

Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.

The same capability is reachable from the application, the API and the agent surface without a second implementation.

Surfaces REST · MCP · CLI

04. Evaluation 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

05. SDK, API, MCP and CLI access

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

A capability in a specification is not a shipped feature.

Interfaces, permission model, evidence requirements, failure modes and the conformance checks a release must pass.

Running deployments, measured performance, third-party certifications or integration approvals.