> For the complete documentation index, see [llms.txt](https://cypher-hub.gitbook.io/cypher-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cypher-hub.gitbook.io/cypher-hub/network-lifecycle.md).

# Network Lifecycle

Every creator journey in CypherHub is automated and transparent.

From onboarding to reward extraction, each phase follows a clear lifecycle.

{% hint style="info" %}
The system evaluates profile quality, surfaces relevant opportunities, and unlocks rewards on a rolling cycle.
{% endhint %}

### Lifecycle phases

{% stepper %}
{% step %}

#### Phase A — Authorization

**Timeline:** 24 hours

Your social profile goes through a deep audit.

The system evaluates your potential and assigns the initial **Pioneer** rank.
{% endstep %}

{% step %}

#### Phase B — Synchronization

You receive personalized campaign notifications, or **signals**, by email.

Speed matters because campaign slots are limited.
{% endstep %}

{% step %}

#### Phase C — Validation and Extraction

Once you publish, the system begins tracking performance.

Rewards accumulate in the **Cargo Hold** balance.

They become available for extraction every 24 hours.
{% endstep %}
{% endstepper %}


---

# 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, and the optional `goal` query parameter:

```
GET https://cypher-hub.gitbook.io/cypher-hub/network-lifecycle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.