A node becomes schedulable only after its identity, runtime and workload capabilities have been evaluated. A hardware declaration is a claim to inspect. A successful challenge demonstrates the properties tested by that challenge, not the execution history of every customer task.
Swipe or scroll to view all columns →
| Stage | Required evidence | Decision |
|---|---|---|
| Registration | Provider identity, node identifier, accountable operator and registered key | Create a declaration under review |
| Environment inspection | OS, CPU or GPU, memory, drivers and runtime artifact digest | Match a versioned support profile |
| Workload qualification | Fixed test inputs, outputs, runtime version and failure logs | Qualify specific workload profiles |
| Isolation review | Privilege, mount, network and resource-limit checks | Confirm the execution boundary |
| Continuing checks | Health observations, service probes, capacity changes and delivery failures | Retain, restrict or suspend eligibility |
Eligibility lifecycle#
The proposed states are declared, under_review, eligible, draining, quarantined and revoked. Only eligible nodes may receive new assignments. Draining stops new work while permitted work finishes. Quarantine suspends eligibility pending investigation. Revocation invalidates admission; reinstatement requires a new review record.
NODE-01 Runtime changes, key revocation, stale critical observations and resource changes MUST trigger an eligibility review. A previous pass MUST NOT substitute indefinitely for current evidence. NODE-02 Admission results MUST identify the test version, observed environment, decision and limitations.
Scope of checks#
The organization of this process draws on io.net's resource-verification documentation and Aethir's separation of registration, standby and in-service checks. Ocean6 does not inherit their algorithms, operating intervals, device requirements or verification guarantees. [R1][R2]
Minimum hardware, challenge design, check frequency and oversubscription policy remain release decisions. They must follow workload measurements and failure analysis. No certified Ocean6 hardware support matrix is published by reference 0.2.