> For the complete documentation index, see [llms.txt](https://oceanea.gitbook.io/oceanea-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oceanea.gitbook.io/oceanea-litepaper/user-journey/node-operator-path/node-partner-roles.md).

# Node Partner Roles

### Service Provider Participation Layer

Node Partner Roles are designed for ecosystem participants capable of providing long-term services, infrastructure, operational support, or ecosystem growth.

The current framework includes four major node categories:

#### Community Nodes

Responsible for:

* Community expansion
* User onboarding
* Community operations
* Ecosystem growth support

#### Content Nodes

Responsible for:

* Strategy creation
* Video production
* Educational content
* Ecosystem media contribution

#### Device Nodes

Responsible for:

* Hardware deployment
* Device maintenance
* Equipment operations
* Usage support

#### Scenario Nodes

Responsible for:

* Dive-shop service fulfillment
* Offline scenario operations
* Experience coordination
* Real-world service integration

***

### Revenue Structure

Depending on participation type, node partners may participate in ecosystem revenue mechanisms including:

* Referral commissions
* Content incentives
* Usage-fee sharing
* Service-order revenue participation
* Ecosystem growth incentives

***

### Qualification Mechanism

Node participation requires:

* Ecosystem application
* Qualification review
* Operational capability assessment

Oceanea Pass holders may receive participation priority under certain ecosystem conditions, but pass ownership does not automatically grant node qualification.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://oceanea.gitbook.io/oceanea-litepaper/user-journey/node-operator-path/node-partner-roles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.