> 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-37.md). # Week 37 * Additional Business Structure documentation produced for internal processes * Road Map - in progress * White Paper - in progress * Leads for reactor continue to progress well * Secret ARC NFT collection dropping #soon * Reactor documentation in roll-out phase * Creating more clips for the Reactor documentation * Generating marketing assets and logo renders for ARC Reactor * Business Development continuing at an increasingly interesting pace * Met with potential ecosystem chain partners * Doubled the amount of people in our giveaway for a trip to London to meet football legends in person and win 1,000,000 $ARC * Signed up for deeper media database research to expand our media relationships * Launched developer portal and assets * Finalized press release for this week, ready to ship * Increased email database by over 1,000 members --- # 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-37.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.