Skip to content
Ocean6Documentation
DocsOperate
Proposed specificationUpdated 19 Sep 2026

Capability profiles and resource claims

On this page
Design status

This chapter specifies proposed network behavior. It is not a deployed service or a production API contract.

A capability profile states what a node is configured to run and links that claim to admission evidence. Keep installed capacity, currently allocatable capacity and observed workload performance as separate measurements.

Swipe or scroll to view all columns →

Field groupRequired contentValidation rule
Identityprovider_id, node_id, key_idResolve through the trusted registry
Runtimeruntime_version, artifact_digestPin the executable artifact
Locationregion and permitted data scopesMatch task policy; record the source of the claim
HardwareCPU or GPU model, count, memory and VRAMUse explicit units and inspection evidence
WorkloadsSupported profile names and versionsAdmit each profile independently
CapacityAvailable resources and reservationsReconcile against active leases
ConnectivityNetwork policy and service probesDistinguish reachability from service readiness
EvidenceTest identifiers, timestamps and evidence referencesReject expired or incompatible evidence

Resource accounting#

CAP-01 Capacity reservations MUST be updated atomically with lease allocation or through an equivalent consistency mechanism. Two coordinators MUST NOT reserve the same exclusive resource concurrently. Shared accelerators require an explicit partitioning and interference policy.

A device count is not a portable unit of compute. Qualification SHOULD name the model, runtime, precision, input size and concurrency used in a measurement. A node qualified for a small retrieval task is not thereby qualified for model inference or training.

Operator actions#

Operators should drain a node before planned maintenance, preserve failure evidence before redeployment and rerun affected qualification tests after changing drivers or runtime artifacts. Emergency isolation may interrupt work; the coordinator must retain the interrupted attempt and its billing context.

The reference bundle contains an unpopulated capability template. It is a documentation aid, not a registered provider, a completed hardware test or evidence of available network capacity.

Documentation 1.1 · Software reference 0.2
Download PDFDeveloper packageWord editionView Markdown

Search across all 30 chapters.

Use Tab to navigate results and Enter to open a chapter.
Documentation v1.1 · EN
Open task lab ↗Ocean6 website ↗