> For the complete documentation index, see [llms.txt](https://zombie-chains.gitbook.io/zombie-fight-club-dead-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zombie-chains.gitbook.io/zombie-fight-club-dead-whitepaper/the-team.md). # The Team • **The Zombie Chains Community DAO** – The Visionaries • **WeirdOZ** – The Builders • **jcardanofan** – The Idea Man: Creator of the Tournament Layout and Economic Flow. • **Vohnj** – Communications Lead: The voice behind sharing the project. Also assists with keeping the DAO communication flow • **HoArder** – The Glue: The man that has allowed us to bring our vision to reality • **beastman.kojak** – Lead Developer: Webpage development and builder of the Tournament Layout • **gary** – Developer/Advisor: Assisting on testing the flow. Bringing additional minting aspects to the Tournament system **The Kreep** – Artist/Advisor: Creator of all the Art NFT’s directly associated the Zombie Fight Club Tournament. • **The Zombie Chains Team** - They are not currently associated with building the Tournament Ecosystem, but without the Art of Brian Allen and the creation of the Fight Simulation by CardanoDan and Chris (reliablestaking) none of this would be possible. --- # 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://zombie-chains.gitbook.io/zombie-fight-club-dead-whitepaper/the-team.md?ask=&goal= ``` `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.