Skip to content
Ocean6Documentation
DocsArchitecture
Proposed specificationUpdated 19 Sep 2026

Roles and trust boundaries

On this page
Design status

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

Every privileged operation MUST be attributable to a tenant, service principal or operator. A wallet address may support an authentication flow, but it does not by itself authorize data access, workload execution or settlement.

Swipe or scroll to view all columns →

RoleResponsibilityAuthority limit
RequesterSubmit, inspect and request cancellation of tenant tasksCannot read another tenant's objects
CoordinatorEnforce policy, allocate capacity and maintain task stateCannot substitute allocation for delivery evidence
ExecutorRun leased work; submit outputs and usage claimsCannot approve its own delivery or confirm payment
CheckerEvaluate a frozen acceptance profile and record evidenceCannot change the request or transfer customer funds
Accounting serviceReconcile usage, quotes, invoices and payment evidenceCannot infer output quality from a payment
OperatorDeploy, investigate, rotate keys and recover servicesCannot alter historical records without an audit trail

Authorization rules#

AUTH-01 The server MUST derive tenant ownership from authenticated context and verify it on every object operation. Client-supplied ownership fields are untrusted. AUTH-02 Credentials MUST restrict operations, resources and validity periods; executor credentials MUST be scoped to the active task or lease.

Human administrators and service accounts SHOULD use separate credentials and audit categories. Changes to production artifacts, billing policy, settlement permissions or quarantined-node eligibility SHOULD require independent review. Review records identify the actor, approver, affected version and reason.

Trust assumptions#

The proposed coordinator is authoritative for state ordering and lease generations. A trusted registry binds provider identities to keys. External model providers remain trust dependencies. Evidence signed by an executor establishes an attributable statement; it does not independently establish hardware identity, model quality or correct execution.

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 ↗