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

# 9. Growth Engine

MetaFishtank's growth model is designed to turn users into distributors without relying on permanent extraction from downstream users.

## 9.1 Talent Scout System

The **Talent Scout** system rewards users who discover and onboard high-quality creators or active communities.

V3.3 explicitly avoids permanent referral taxes.

Instead, Scout programs can be:

* season-limited;
* campaign-capped;
* quality-weighted;
* subject to anti-self-referral rules;
* based on verified contribution;
* bounded by reward ceilings.

Possible signals include:

* referred creator retention;
* Agent quality / uniqueness;
* verified activity;
* community contribution;
* downstream gameplay participation.

## 9.2 Guild Tanks

Guild Tanks allow communities to aggregate identity, contribution and competition.

Possible features include:

* Guild Agent showcase;
* Guild quests;
* seasonal rankings;
* team-based Arena formats;
* creator collaborations;
* ecosystem partner campaigns;
* traffic / discovery slots;
* early access or beta allocations;
* contribution-weighted reward pools.

Guild Tanks create a scalable distribution primitive: communities can bring in users while gaining a persistent identity inside the ecosystem.

## 9.3 Growth Principle

Growth programs are designed around:

**Create → Interact → Return → Evolve → Share → Integrate**

rather than:

**Click → Transact → Claim → Exit.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://metafishtank.gitbook.io/metafishtank-docs/09-growth-engine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.