> For the complete documentation index, see [llms.txt](https://docs.insertnonsense.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.insertnonsense.com/readme.md). # ONCHAIN NONSENSE — Player Guide Ridiculous games. Real receipts. **Play:** [insertnonsense.com](https://insertnonsense.com) · **Contact:** This guide covers the **Base mainnet** deployment (chain 8453). The interface is maintained anonymously; the contact email is not a verified legal identity. Review the live contract manifest before signing. [Terms](https://insertnonsense.com/legal/terms.html) · [Privacy & storage](https://insertnonsense.com/legal/privacy.html) · [Game risks](https://insertnonsense.com/legal/risks.html). These notices are published as unreviewed drafts, not a statement of legal approval. ONCHAIN NONSENSE is an onchain arcade: own a square until someone buys it away, swing at a shared boss, or build a circuit that might catch a randomly selected spark. Wallets submit transactions; contracts record ownership, entries, and payouts. > **Real assets at risk.** Games use native USDC on Base mainnet and ETH for gas. Entries can lose their entire stake. Tests and verified source are not an independent professional audit or a guarantee of security. No token or airdrop entitlement is promised. ![The mainnet arcade homepage with The Pixel, The Piñata, The Frequency, and The Fuse](https://177677568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG1XFXI0IB5XtUnzOGkjF%2Fuploads%2Fgit-blob-2a0fe56d10b40f56f67963558b58033a552ef1de%2Fmainnet-arcade.png?alt=media) *Actual browser capture from insertnonsense.com on Base mainnet. The Frequency is a preview, not a playable game. Values and availability can change after these screenshots.* ## Contents * [Start here](#start-here) * [Choose your game](#choose-your-game) * [The Pixel](#the-pixel) * [The Piñata](#the-piñata) * [The Fuse](#the-fuse) * [The Frequency](#the-frequency) * [Profiles and sharing](#profiles-and-sharing) * [Tokens and future features](#tokens-and-future-features) * [Safety and trust assumptions](#safety-and-trust-assumptions) * [Troubleshooting](#troubleshooting) * [Contracts and verification](#contracts-and-verification) ## Start here ### 1. Prepare a wallet Use an Ethereum-compatible wallet supported by the app. A dedicated low-balance wallet is recommended. You do not need to create an arcade password or give the app your recovery phrase. Open the app through a verified project link, select **Connect Wallet**, and choose your wallet. If a wallet is not installed, the connection dialog may display an installation link. Check the destination before installing anything. ![Wallet connection dialog showing supported wallet choices](https://177677568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG1XFXI0IB5XtUnzOGkjF%2Fuploads%2Fgit-blob-46d57baed0d194cd1f400c218bcc659a38e3b5e1%2Fconnect-wallet.png?alt=media) *This screenshot was taken in a browser without wallet extensions, so the choices display “Install.” An installed wallet may behave differently.* ### 2. Use Base mainnet | Setting | Value | | ------------------- | --------------------------------- | | Network | Base mainnet | | Chain ID | `8453` | | Native gas currency | ETH on Base | | Public RPC | `https://mainnet.base.org` | | Explorer | [Basescan](https://basescan.org/) | | Game currency | Native USDC, 6 decimal places | Check these settings against [Base's official RPC documentation](https://docs.base.org/base-chain/api-reference/rpc-overview). Base mainnet, Ethereum mainnet and testnets are different networks: balances do not automatically transfer between them. Fuse requires no Ethereum Sepolia deployment or bridge for randomness. ### 3. Check your funds and limits You need ETH on Base for gas and the native USDC address listed below for paid actions. Faucet tokens and testnet balances do not work here. If transferring assets, independently verify the destination network and token through your chosen provider; do not follow unsolicited bridge or funding links. Only use money you can afford to lose. No project token purchase is required. Do not transfer assets directly to game contracts: use the documented game functions through a verified interface. ### 4. Understand the transaction flow 1. Choose an action and review its USDC price. 2. If prompted, approve the game contract to spend the required USDC. 3. Confirm the actual game transaction. Approval alone does not place a tile, buy a swing, or enter a round. 4. Wait for confirmation. Randomness-based actions also need a later oracle fulfillment and, for Fuse, settlement. 5. Claim any available payouts through the game's claim controls. Some supported wallet flows may bundle steps. Always inspect the requested network, contract, and spending amount. ETH gas is separate from the USDC price; reverted transactions can still consume gas. ## Choose your game | Game | What you do | Current status | App route | | ------------- | -------------------------------------------------------------------------------- | -------------------------------- | --------------------- | | The Pixel | Claim artwork tiles, buy tiles from their owners, and collect eligible proceeds | Base mainnet | `/pixel` | | The Piñata | Damage a shared boss; the finishing swing and recent swing slots receive payouts | Base mainnet, Chainlink VRF | `/pinata` | | The Fuse | Place a wire, connect a circuit, and await a random perimeter spark | Base mainnet, Chainlink VRF | `/fuse` | | The Frequency | Proposed sealed-choice coordination game | Coming soon; rules are not final | Homepage preview only | Routes above are paths on the arcade website, not links to pages on this documentation site. Deployment and source verification are not equivalent to a professional security audit. ## The Pixel **Own a square of the internet. Until someone pays double.** ![The Pixel's mainnet 3D wall and controls](https://177677568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG1XFXI0IB5XtUnzOGkjF%2Fuploads%2Fgit-blob-21e7ac6b735622bf34833f3d5fa5e774ebebb060%2Fmainnet-pixel.png?alt=media) *The newly launched wall has no purchased tiles: the gray board and 0/2,304 counter reflect onchain state, not missing artwork.* ### Claim a tile The wall contains **48 × 48 tiles**, or **2,304 positions**, with IDs from `0` to `2303`. Select a tile on the wall, or use the tile-ID control when precise selection is easier. Choose the available artwork options, including color, emoji, message, and optional link; review the quote and purchase. The normal price of the next unclaimed tile starts at **5 USDC** and increases by **0.25 USDC per paid first sale**. It is a wall-wide price, not a separate starting price for each location. Resales use different pricing. A multi-buy can include up to 32 tiles, priced sequentially; it is not 32 copies of the initial quote. Messages are limited to 80 UTF-8 bytes and links to 160 bytes. Some characters use more than one byte. Links must be valid HTTPS links meeting the contract's restrictions. Ownership and submitted content are public; do not put private information on a tile. ### Buying an owned tile An unshielded tile can be bought away from its owner for **twice its last purchase price**. The owner cannot refuse a valid purchase. You cannot buy your own tile through this mechanism. Under the default split, 90% of that purchase goes to the previous owner's withdrawable balance and 10% is the house portion. For example, a tile last purchased for 5 USDC costs 10 USDC to take over, with 9 USDC credited to its previous owner under that split. This is not an immediate wallet transfer: claim the available balance afterward. A higher asking price is **not a guaranteed sale or profit**. Another player must actually buy the tile. Special preseeded tiles have a different first-sale beneficiary; do not assume every previous displayed owner receives that first payout. ### Tile yield Eligible purchased tiles also share a portion of qualifying protocol income. The default allocation is 20% of eligible house inflows; the treasury can change the future rate within the contract's 0–50% bounds. This is separate from the previous-owner payment on a resale. Rewards are allocated per eligible tile, not according to its artwork or purchase price. A new owner does not receive the previous owner's historical accrual. Whole claimable amounts accrued before a forced sale remain available to the previous owner. Synthetic preseeded tiles do not earn until purchased. Yield depends on activity. It is not interest on a deposit, a fixed APR, or a promise that buying a tile will recover its cost. Base-unit rounding can leave small amounts in the protected reward reserve. ### Shields, mystery buys, and auctions * **Shields:** temporary protection against takeovers. The configured cost is **1 USDC per block**, not per hour. A purchase can add 1–43,200 blocks. Review the total carefully: 10 blocks costs 10 USDC. A shield cannot reverse a takeover confirmed before it. * **Mystery buy:** selects an available tile with a 15% discount against the normal next-tile price. This selection is not Chainlink VRF and should not be treated as equally strong randomness. Its bounded search can fail even when other positions remain available. * **Auctions:** available when the treasury opens one for an unclaimed tile. Bids must increase by at least 5%, rounded up. Late bids can extend the auction. Outbid bidders claim their refunds separately. The winner can settle with their artwork after the deadline; after the grace period, anyone can settle with defaults. Auction proceeds split 50% to tile yield and 50% to treasury. If another transaction changes a price or takes a selected tile before yours executes, the purchase can revert rather than exceed your signed limit. An unavailable tile can also cause an entire batch to revert. ## The Piñata **One boss. A shared health bar. A pot waiting for the finishing swing.** ![The mainnet Piñata arena showing the boss, integrity, pot, swing price, and prediction controls](https://177677568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG1XFXI0IB5XtUnzOGkjF%2Fuploads%2Fgit-blob-332bfc0f37cab784c986bf6d25d678cc9b57b968%2Fmainnet-pinata.png?alt=media) *The screenshot shows the undamaged mainnet boss, an empty pot, and the initial 2 USDC swing price. Different boss artwork represents generations of the same game.* ### Swing, wait, repeat 1. Review the current health, swing fee, and pot. 2. Approve USDC if needed and submit a swing. 3. Wait for Chainlink VRF to resolve the hit. A confirmed request is not yet a damage result. 4. Review the resolved damage, any combo or critical hit, and the updated pot. 5. If credited with winnings, use the claim control to withdraw them. Only one swing request can be pending globally at a time. Other players must wait for that request to resolve. The initial swing costs **2 USDC**. The fee rises by 4% after a fulfilled swing, subject to integer rounding and a 512 USDC cap, and resets for the next boss. Under the currently configured split, 90% of a fulfilled swing fee enters the pot and 10% goes to reserves. Some economic settings are configurable within contract limits; the current quote and deployment are authoritative. Bosses start with 100 HP. Base damage spans 4–10 HP before generation scaling, combos, and critical hits. Generation scaling increases by 6% per generation up to 3×. A wallet's qualifying repeated resolved swings within the 25-block combo window gain 10% per additional combo step, up to a 100% bonus. Critical outcomes include 2.5× and 5× hits; they are not player-selected. ### When the boss breaks The pot is allocated as follows: | Recipient | Share | | ------------------------------------- | --------------------------------------------------- | | Wallet delivering the finishing swing | 80% | | Last three fulfilled swing slots | 10% shared between slots | | Reserves | 10%, plus applicable rounding or empty-slot amounts | The recent slots are **not necessarily three distinct people or wallets**. A wallet can occupy multiple slots, and the finishing wallet can also qualify through recent slots. Payouts are credited for withdrawal; keep enough ETH on Base to claim. ### Side bets and pot seeding Side bets predict whether the boss breaks **on or before a chosen swing number**, not on exactly that swing. They close when the first swing request of the generation begins. The configured limits are ten bets per generation and three per wallet. Winning stakes share the betting pool proportionally after a 5% house fee. A prediction that fails loses its stake. If no bets qualify as winners, the pool goes to reserves. Side bets are separate from the main finishing-swing pot. Seeding the pot is a contribution to the game, not a refundable deposit or a purchase of better winning odds. ### Deployment-specific recovery warning The mainnet Piñata supports `retired()` and a delayed treasury-controlled retirement/refund path for prolonged VRF failure. It does not offer automatic refunds for ordinary losing swings or bets. The callback gas allowance is 900,000, increased after a cold-storage regression exceeded the former 400,000 allowance. Crack bets require at least 1 USDC. Ten total slots and three per wallet are not Sybil resistance; higher swing ceilings are easier to satisfy and pooled returns are not balanced fixed odds. ## The Fuse **Build a shared circuit. A random edge ignites. Connected builders may win.** ![The mainnet Fuse board, round information, and explanatory panel](https://177677568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG1XFXI0IB5XtUnzOGkjF%2Fuploads%2Fgit-blob-c6ba8adffb582b2390fb06765cc4c94c994be40f%2Fmainnet-fuse.png?alt=media) *This capture shows the first live mainnet round with no purchased wires. “0 blocks remain” requires round advancement; a clock reaching zero does not submit a blockchain transaction. Local fallback selections never represent paid entries until the transaction confirms.* ### Build phase The board is **8 × 8**, labeled A1–H8. Each wallet can place **one wire per round**, paying **1 USDC**. A round closes after 1,800 blocks or when all 64 positions are filled. One wallet is not necessarily one person. Choose a straight or corner wire. Each shape has exactly two ports. Adjacent tiles connect only when both ports face each other; diagonal neighbors and opposite board edges do not connect. There are no T-junctions or four-way crossings. You can select **one to four ordered fallback positions**, with a wire shape for each. The contract places only the first available choice and charges one entry fee. These choices are not reservations. If all are occupied, the round has changed, or its deadline has passed, the entry reverts. A confirmed wire cannot be moved or rotated. One entry per wallet is not one entry per human: someone may control multiple wallets. ### Lock → randomness → settlement → claims 1. **Lock:** after the deadline or a full board, anyone can submit the round-lock transaction. 2. **Too few entries:** with fewer than three tiles, the round does not request randomness. Paid entries become refundable, and the game advances. 3. **Request:** a qualifying locked board requests Chainlink VRF on Base mainnet. Placements are frozen. 4. **Randomness arrives:** the callback stores the random word. This is separate from distributing results. 5. **Settle:** anyone can submit settlement once the word is ready. 6. **Claim:** winning wallets withdraw credited prizes. Refundable wallets withdraw their refunds. Fuse uses Chainlink VRF on **Base itself**, with the configured subscription also serving Piñata. There is no separate Ethereum Sepolia game deployment or cross-chain randomness bridge in this flow. Oracle availability, subscription funding, and transaction inclusion still matter. See [Chainlink's VRF security considerations](https://docs.chain.link/vrf/v2-5/security). ### What makes a winning circuit? Randomness selects one of the board's **32 perimeter edges**, not one of 64 cells. A corner touches two perimeter edges. The selected edge must meet an inward-facing wire port, and its reciprocal connected component must contain **at least three tiles**. If it hits a qualifying path, its tiles receive the calculated per-tile reward. An empty edge, a disconnected port, or an undersized component produces no winning path. A closed loop without an exposed perimeter port cannot catch an outside spark. Because wires have only two ports, a single connected component can expose at most two perimeter endpoints. Even a well-built path is not guaranteed to ignite; its maximum hit probability is 2/32, or 6.25%, when it exposes two valid endpoints. The payout percentages below are not winning probabilities. ### How the payout works At normal settlement, 90% of the round's entry fees are added to the rolling pot and 10% goes to reserves. The prize calculation then uses: ``` available pot = previous rolling pot + 90% of settled entry fees round budget = minimum(90% of available pot, 1,000 USDC) reward per winning tile = round budget / 64, rounded down total paid = reward per winning tile × winning component size ``` **The divisor is always 64, not the number of winning tiles.** “90% budget” does not mean that a short winning circuit receives 90% of the pot. For example, if the available pot after the entry contribution is 100 USDC, the budget is 90 USDC. Each winning tile receives 1.406250 USDC. A four-tile winning path receives 5.625000 USDC in total, leaving 94.375000 USDC in the pot. Unused value rolls forward. A normal missed spark does not refund entry fees. All amounts use six-decimal USDC units, with contract rounding applied. ### Share a circuit Use the sharing controls to send a round-specific link and suggested wire positions. A recipient can inspect the board and choose their own entry; opening the link never signs a transaction or reserves a position. Older or occupied suggestions may no longer be usable. Result and replay controls help show how a spark traveled. A downloadable image is a shareable record, not proof of a guaranteed payout; use the transaction and contract state to verify outcomes. Link previews can be generic rather than personalized for every round. ### Delayed randomness and retirement If randomness has not arrived after more than 14,400 blocks from the request, the treasury can permanently retire this deployment and make pending-round entries refundable. This is an operator action, not an automatic timeout. The rolling pot remains frozen; retirement does not divide it among entrants or restart the game. If VRF cannot create a request and the board remains in Building, the same terminal retirement/refund path becomes available more than 14,400 blocks after its closing block. Once a random word is stored, settlement is mandatory and retirement is unavailable. The callback stores the word with a 150,000-gas allowance; a separate permissionless transaction settles the round. Once the random word has been stored, that missing-randomness retirement path is unavailable and anyone can settle. Pausing stops new value entry, but does not disable the intended lock, settlement, or claim paths. This design still has operational trust assumptions: it is not a promise of instant fulfillment or freedom from all administrator or oracle risks. The current deployment and UI wiring have been checked, but this guide does not certify a completed first live VRF round or a production audit. ## The Frequency **Transmission pending. Not playable yet.** The homepage describes a proposed blind coordination game: secretly choose one of eight channels, reveal the choices together, and let the largest group on a channel share the round vault. The preview mentions Chainlink VRF for tied channels and carrying unclaimed value forward. These are concept descriptions, not deployed rules. There is no playable Frequency contract or game route in this release, and no finalized entry price, payout schedule, reveal procedure, or launch date. A possible variation is **Signal Crews**: small invited groups coordinate their choices and share a reveal result. That is a brainstormed direction, not an available private-chat or crew feature. Final mechanics must be documented and tested before anyone is asked to pay to play. “Last Vibe Standing” was an earlier concept, not an additional active game in this release. ## Profiles and sharing The username registry lets a wallet set a public display name of 1–24 ASCII characters using letters, digits, underscores, and periods. There is no protocol registration fee, but setting a name requires gas. Names are not unique and do not verify identity. Always use wallet addresses and transaction records when identity matters. Invite people to an actual game moment: a wire placement, a boss result, or a specific tile. Let them inspect the action and cost before signing. A shared link is not authorization to spend from the recipient's wallet. Social distribution features remain deployment-dependent. A fully published Base/Farcaster Mini App, opt-in notification delivery, referral rewards, and the proposed Signal Crews system are **not promised as live features by this guide**. A practice-labeled build uses demonstration state rather than real entries. Mainnet screenshots do not demonstrate a completed paid transaction. ## Tokens and future features You may notice cryptic token references in the interface. They are flavor and hints about possibilities—not confirmation of a token launch. There is currently no confirmed token ticker, launch date, supply, allocation, purchase eligibility, snapshot, airdrop, staking reward, or governance entitlement documented for this release. Playing or sharing does not create a right to a future reward. Some contracts include optional token-related configuration hooks. Their existence does not mean token-holder discounts or access benefits are enabled in the current app. Treat unsolicited “claim,” presale, migration, or snapshot links as suspicious and verify any future announcement independently. ## Safety and trust assumptions * **Public by design:** wallet activity, game transactions, usernames, and submitted onchain content are observable. Linked websites have their own privacy and security risks. * **Wallet custody is not contract-risk immunity:** the app does not need your keys, but funds approved or paid to contracts are exposed to those contracts and their dependencies. * **No absolute security claims:** testing, fuzzing, invariant checks, and security review reduce risk; they cannot prove a complex deployed system non-exploitable or non-griefable in all circumstances. * **Administrator powers matter:** treasury and pause roles can affect available actions and selected economic settings. Distinct labels do not guarantee independent operators. Check the deployed roles and permitted functions. * **Randomness is asynchronous:** a request can wait on funding, oracle delivery, or network conditions. Chainlink VRF does not make transaction ordering fair or remove every economic attack. * **Claims need transactions:** credited winnings and refunds may remain in contract accounting until withdrawn. Keep ETH on Base for gas. * **Do not assume refunds:** losing entries, failed predictions, voluntary pot contributions, and ordinary missed Fuse sparks are not automatically refundable. * **Documentation can lag:** check the network, contract address, live quote, and verified implementation before signing. A legacy deployment can differ from current repository source. Never share a recovery phrase, private key, wallet export, or remote-access session with someone claiming to provide support. Use a dedicated low-balance wallet: compromised signing keys can also endanger assets on other networks. ## Troubleshooting | What you see | What to check | | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Wrong network or missing balance | Switch to Base mainnet, chain 8453. Confirm the token address below; testnet and Ethereum balances are separate. | | Insufficient gas | You need ETH on Base. USDC cannot pay the normal gas fee. | | Insufficient USDC | Check native USDC on Base and your connected address; faucet assets are not mainnet USDC. | | Approval succeeded, but nothing happened | Submit the actual purchase or entry transaction. Approval is only spending permission. | | Price changed or tile unavailable | Refresh the quote and selection. Another transaction may have executed first. Do not blindly increase spending limits. | | Pixel takeover rejected | Check shields, ownership, and the latest takeover price. | | Piñata says randomness is pending | Wait for fulfillment and inspect the request transaction. Another swing cannot bypass the pending request. | | Fuse shows 0 blocks remaining | The deadline passed. Someone must submit the permissionless round advancement transaction. | | Fuse has randomness but no result | Settlement still needs a transaction; anyone can submit it. | | Fuse previews disappeared or entry reverted | Fallbacks are not reservations; cells may have been taken or the round may have changed. | | Winnings are visible but wallet balance is unchanged | Use the applicable claim/withdraw control and wait for its receipt. | | UI looks stale or disagrees with your wallet | Check the transaction on the explorer, then refresh. RPC/indexing delays can affect displayed data. | | Game is paused or retired | Do not keep resubmitting entries. Check contract state and available claim/recovery paths; retirement is not a temporary pause. | For a useful bug report, include the game route, chain ID, approximate time, transaction hash, exact error, and a screenshot. A public wallet address can help if you are comfortable sharing it. Remove unrelated balances, personal information, and all secrets. Use only a support channel linked from the verified project website. ## Contracts and verification These are the **Base mainnet** contracts. Their source is verified on Basescan. Use supported functions, not direct token transfers. Verify contract addresses and transactions using the explorer links below. | Component | Address / explorer | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | Pixel | [0xEE68FF43ed2D7306D10F5C012A3251f2D49C7AD2](https://basescan.org/address/0xee68ff43ed2d7306d10f5c012a3251f2d49c7ad2#code) | | Piñata | [0x95aCAFE4Cfb7e75A77Ada68C91f3D7c4E2CeD142](https://basescan.org/address/0x95acafe4cfb7e75a77ada68c91f3d7c4e2ced142#code) | | Fuse | [0x848576d65C3562f1c1425148C2A37A4c9F29626e](https://basescan.org/address/0x848576d65c3562f1c1425148c2a37a4c9f29626e#code) | | Usernames | [0x6C61C2c0E6DFbF34e13Dd3EAC2B12cD530f04045](https://basescan.org/address/0x6c61c2c0e6dfbf34e13dd3eac2b12cd530f04045#code) | | USDC | [0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913](https://basescan.org/address/0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) | | Chainlink VRF coordinator | [0xd5D517aBE5cF79B7e95eC98dB0f0277788aFF634](https://basescan.org/address/0xd5D517aBE5cF79B7e95eC98dB0f0277788aFF634) | An explorer transaction receipt shows whether a transaction succeeded; it does not by itself establish that a later VRF callback or payout claim also happened. Verify those stages separately. ### Screenshot and artwork credits Mainnet game screenshots were captured from insertnonsense.com on September 8, 2026. The wallet installation-dialog illustration is retained from the September 7 preview. No paid game transaction was submitted to stage these images. The UI includes emoji artwork from [OpenMoji](https://openmoji.org/), an open-source project by the HfG Schwäbisch Gmünd design community, licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). Project adaptations arranging and rasterizing those glyphs retain that license. This attribution concerns the OpenMoji artwork; it does not assign a blanket license to every other interface element or wallet trademark. --- # 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://docs.insertnonsense.com/readme.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.