> 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/01-executive-summary.md). # 1. Executive Summary ## 1.1 The Mission: From Static Assets to Living Agents Digital ownership in Web3 has largely focused on proving who owns an asset. MetaFishtank extends that idea by asking a more important question: > **What can the asset become after it is owned?** Most game NFTs remain static containers of artwork and metadata. Their utility is usually defined by one game, one ruleset and one development team. When that environment loses users or shuts down, the asset may remain transferable while its functional value disappears. MetaFishtank introduces **User-Generated Agents (UGA)**: player-created digital entities whose identity, attributes, behavioral profile, memory state and evolution history can persist beyond a single game. The objective is not to place AI beside a game as a chatbot feature. The objective is to make the **asset itself AI-native**. ## 1.2 The Asset-First Philosophy Traditional games follow a **Game-First** architecture: developers build a world and then create assets for that world. MetaFishtank inverts this model. In an **Asset-First** architecture, the Agent is the persistent constant and the game is a replaceable environment. * **Creation First:** Users create the first generation of Agents through low-barrier applications such as Drawafish. * **Portable Identity:** Every Agent has a persistent identifier, verifiable ownership, structured traits and an evolving state profile. * **Reusable Utility:** Compatible games can read the same Agent through the MetaFishtank Asset Protocol (MAP). * **Controlled Write-Back:** Approved games can contribute new state, achievements, skills or experience back to the Agent under explicit protocol permissions. * **Developer Cold-Start Reduction:** New games can integrate an existing asset and user base rather than issuing another isolated NFT collection. > **The Agent remains constant. The game becomes interchangeable.** ## 1.3 The MetaFishtank Stack MetaFishtank is organized into three functional layers. These names describe responsibilities rather than blockchain layers. ### MAP — Protocol Layer The portable asset and state standard. MAP defines how Agent identity, immutable DNA, mutable traits, permissions, verification status, game namespaces and cross-game evolution are represented and accessed. ### Anima Engine™ — Intelligence Layer The interpretation and behavior engine. Anima converts user expression into structured Agent data, generates behavior profiles, validates creation inputs, supports developer-side Agent generation and produces signed state payloads that can be committed to MAP. ### Tank Ecosystem — Application Layer The runtime and distribution environment for official and third-party games. Games consume MAP state, invoke Anima capabilities and—when authorized—write meaningful evolution back to the Agent. ## 1.4 The Strategic Moat MetaFishtank's defensibility is designed around five reinforcing assets: * **Behavioral Dataset:** A growing proprietary dataset mapping user-created visual structures and interaction histories into normalized game attributes and behavior profiles. * **Agent State Graph:** Every Agent accumulates a verifiable graph of creation, interaction, achievements, skills, game participation and evolution. * **Protocol Network Effects:** Every additional game that reads MAP increases the utility of existing Agents; every additional Agent makes MAP more attractive to developers. * **Developer Distribution:** SDKs, adapters, reference games and reusable Agent inventory reduce the cost of launching AI-native game experiences. * **Intent Intelligence:** Over time, the mapping between human expression and machine-readable behavior can evolve into a specialized model layer with potential value beyond any single game. ## 1.5 What MetaFishtank Is — and Is Not MetaFishtank is **not a new blockchain, rollup, or Layer 2**. It is an application and middleware infrastructure stack deployed on existing blockchain infrastructure. The initial on-chain deployment is built on **BNB Smart Chain (BSC)**, while the architecture remains modular enough to add additional execution environments in the future without changing the core UGA model. > **BNB Chain provides the execution environment. MAP defines the asset language. Anima gives the asset life.** --- # 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/01-executive-summary.md?ask=&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.