> 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-27.md). # Week 27 * We've been ramping up our video content creation as we make new videos in preparation for the NFT Marketplace launch. * We've been working on the new ARC Reactor 3D model animation in preparation to feature it on the new website. * We've created plans around technologies and structure for development of the new landing page to better encapsulate the ARC brand. * Further development on the reactor including additions such as the compiler API, ARC VM and scripts that perform an automated mathematical proof that ARC VM generated source code fulfills a certain formal specification via the diagrams. * The marketplace has had some minor UI updates and scheduled to release many more UI updates on a larger pull request later in the month * Transition of associate role into sales pipeline and structure * Phase 1 Marketplace partner preparation ongoing --- # 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-27.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.