> 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-39.md).

# Week 39

* Sales videos for Reactor are complete and are currently in marketing review
* Upcoming AMA today will be recorded and uploaded to YouTube
* We're generating more marketing material for the reactor specifically focusing on content showcasing before/after reactor examples
* Pushed PR release on new advisory board member to go live today 29 September
* Moved conversations with exchanges forward
* Prepared for announcing JUP airdrop
* Prepared for JUP AMA setup
* Collaborated with influencers
* Assisted in onboarding new marketing assets and role
* Explored partnerships with crypto academies
* Community AMA
* updates on ARC stale UI
* ARC 30days subscription in USDC
* ARC GH push save


---

# 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-39.md?ask=<question>&goal=<endgoal>
```

`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.
