> For the complete documentation index, see [llms.txt](https://arc-3.gitbook.io/arc-newsletter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arc-3.gitbook.io/arc-newsletter/week-30.md). # Week 30 * Worked on launch graphics for our partners, JUP Apes and StarCard Sports Games * We are creating a logo for the ARC Reactor to be used as a standalone logo in addition to the main ARC logo * We launched JUP Apes NFT collection, and the NFT MarketPlace * Press release introducing JUP Apes NFT: * Press release for 300k $JUP and rare JUP Ape NFT giveaways: * Press release distribution reports attached * We're definitely seeing a shift in sentiment on all fronts, even from some who left the ARC community and hodler ranks, returning with open minds and hearts * We launched landing pages for partner projects. You can see the first one here for JUP Apes: * SCSG Launch of the Diamond Palla Ball series & Scarves --- # 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://arc-3.gitbook.io/arc-newsletter/week-30.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.