Ocean6 is developing a service network for coordinating AI workloads, compute providers and external systems. Its proposed protocol connects a defined task to an authorized executor, an inspectable delivery record, a separate acceptance decision and an attributable charge.
This documentation describes the system architecture and the engineering requirements for that network. It also provides an executable local reference that developers can inspect and reproduce today. The reference implements deterministic text retrieval; it establishes a narrow, testable foundation for input validation and result verification.
Swipe or scroll to view all columns →
| Capability | Availability | Evidence |
|---|---|---|
| Local text retrieval | Implemented in reference 0.2 | Python and JavaScript implementations; task schema; fixtures |
| Local replay and byte integrity | Implemented in reference 0.2 | Independent Python replay and SHA-256 checks |
| Node admission and scheduling | Proposed | Protocol requirements and acceptance cases |
| Remote AI and GPU execution | Not demonstrated by this release | Requires a deployed runtime and workload records |
| Authenticated receipts and payments | Proposed | Requires identity infrastructure, signed records and reconciliation |
| TEE or zero-knowledge guarantees | Research option | Requires a defined trust model and implementation evidence |
How to use this documentation#
Start with the architecture and trust model, then run the local quickstart. The network chapters use the label Proposed specification. These chapters define requirements for a future implementation, not a public API contract. Reference 0.2 chapters describe the released local behavior.
MUST, MUST NOT, SHOULD and MAY express requirement levels when capitalized, following BCP 14. A requirement in a proposed chapter is not a claim that the control is deployed. Documentation version 1.1 and software reference version 0.2 are separate version lines. [S5]
This edition is intended for application developers, infrastructure engineers, node operators and technical reviewers. Hardware pricing, token issuance, staking and reward formulas are outside its scope.