Knowledge & context · Concept

Capabilities with boundaries attached.

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

Status Concept Category Knowledge & context Surfaces REST · MCP · CLI Contact [email protected]

The five contracts

Numbered for reference; the order is not a priority.

01. Context isolation and tenancy

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. Policy-enforced retrieval

Implemented through one permission model that applies to the human interface and the machine interface alike.

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

Surfaces REST · MCP · CLI

03. Sensitive-data controls

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

04. Context lifecycle and revocation

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

Scope is attached to the capability, not to the caller, so delegation does not widen it silently.

Surfaces REST · MCP · CLI

05. Evidence-backed context authorization

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

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

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.