# Welcome to Beezlebop's Briefing! {% hint style="info" %} Join Beezlbop's Brigade, the Discord server for Beezlebop's Blunder, to join the community and provide feedback!\ \ {% endhint %} ## Overview Welcome Adventurer! This Gitbook space is being built as a living Game Design Document / Whitepaper and will serve as all-in-one informational resource for **Beezlebop's Blunder**, an Axie Infinity game currently being built by w0nd3r.eth! **Beezlebop's Blunder** is being designed and built in 2 complementary layers: * Layer 1 presents the Free 2 Play (F2P) components which underlie the core mechanics of the game that all players will have access to * Layer 2 presents the Token-Gated Porgression (TGP) components that augment the core experience with progressive elements that extend across gameplay sessions (and more?!). Its also worth noting that the development process has been and will continue to be augmented by generative AI tools for the production of code (game logic, UI/rendering), game assets (world, items, etc.), and business plan formation and execution. The development plan is designed to rapidly build, in the open, and iterate with player feedback on the core design components, prioritizing a product that is initially low fidelity and high complexity. Then as the game develops and the mechanics are sharpened, the art and aesthetic will transition from low to high fidelity while retaining the underlying complexity. All together, **Beezlebop's Blunder** is an experiment that seeks to integrate many of the cutting edge technologies available today, and rapidly integrate new ones as they are developed, in order to meaningfully contribute to the web3 gaming space. The pages within this section lay out the high level concept map of **Beezlebop's Blunder** including core design features and build phases. {% hint style="info" %} NOTE: All information and numerical values discussed throughout the following sections are subject to change throughout the development process. {% endhint %}

Phase 0 Demo - Axie Builders Program Application (mobile)

{% content-ref url="welcome-to-beezlebops-briefing/table-of-contents" %} [table-of-contents](https://briefing.beezle.buzz/welcome-to-beezlebops-briefing/table-of-contents) {% endcontent-ref %} {% content-ref url="welcome-to-beezlebops-briefing/core-design-features" %} [core-design-features](https://briefing.beezle.buzz/welcome-to-beezlebops-briefing/core-design-features) {% endcontent-ref %} {% content-ref url="welcome-to-beezlebops-briefing/build-phases" %} [build-phases](https://briefing.beezle.buzz/welcome-to-beezlebops-briefing/build-phases) {% endcontent-ref %} --- # Agent Instructions: 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: ``` GET https://briefing.beezle.buzz/welcome-to-beezlebops-briefing.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.