Specified
Interfaces, permission model, evidence requirements, failure modes and the conformance checks a release must pass.
Knowledge & context · Concept
Capabilities with boundaries attached.
Each capability in GraphNative AI 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. Canonical entity and relationship graphs
-
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
- 02. Graph-based context retrieval
-
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
- 03. Provenance-aware intelligence
-
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
- 04. Semantic reasoning and orchestration interfaces
-
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. Graph analytics, API and MCP access
-
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
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.