> 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/08-cin-retention.md).

# 8. C.I.N. Retention Model

Drawafish is designed around three mutually reinforcing psychological loops:

**Creativity × Interactivity × Nurturing**

## 8.1 C — Creativity: Visual Sovereignty

Users begin by making something rather than buying something.

* **Low Barrier:** Almost anyone can create a recognizable Fish.
* **High Ceiling:** Skilled users can create visually distinctive Agents.
* **Identity:** The visual origin of an Agent becomes personal rather than factory-issued.
* **Endowment Effect:** Creation can increase emotional attachment compared with simply purchasing a pre-made asset.

The system should reward original expression without pretending that visual appearance is a scientifically deterministic predictor of combat power.

## 8.2 I — Interactivity: The Tank as Social Graph

Agents gain relevance when other people can discover, react to and interact with them.

Interactivity can include:

* visiting Tanks;
* feeding or helping neighbors;
* aesthetic discovery;
* social voting;
* Guild activities;
* Arena competition;
* creator challenges;
* cross-game achievements.

The Tank becomes a visual social graph rather than a static wallet gallery.

## 8.3 N — Nurturing: Visible Growth

Users should be able to see the difference between an Agent they created yesterday and one they have developed for months.

Nurturing can produce:

* visual evolution;
* level progression;
* skill unlocks;
* relationship state;
* squad formation;
* cross-game badges;
* persistent memories;
* reputation and creator status.

The satisfaction comes from moving from:

**One simple Fish → A developed Agent → A coordinated Squad → A persistent cross-game identity.**

The C.I.N. model matters because protocol interoperability alone does not create retention. Users must care about the identity being preserved.


---

# 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/08-cin-retention.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.