> 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-29.md). # Week 29 * Onboarded a new community moderator (Sam Malone) and associate (Thomas ZH) in order to boost community engagement and sales * Preparing launches of JUP Apes and SCSG, as well as a number more for Phase 1 MP launch * The progress on the website is an ongoing mission to add greater clarity around our products, mission, progress and team - It’s a hot week all around, especially with partnerships cooking in the kitchen and being served fresh off the grill next week. * Stay tuned as we release more information this week. - watch out for exciting giveaways, staking rewards and more over the next 21 days - AMAs and Twitter spaces are being planned, we are looking forward to connecting with you * Partner pages are launching this week for our upcoming NFT marketplace or tech partnerships, helping us articulate the benefits to ARC token holders and new community members * Started creative development on the ARC Reactor Logo --- # 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-29.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.