> For the complete documentation index, see [llms.txt](https://docs.cyberbrokers.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cyberbrokers.com/user-guide/missions/alpha/qa-m03/summary.md).

# Summary

### Quest #3 Completed!

In Quest #2, Spice set out with Ken and Zinc to spread the bombshell message that CyberBrokers are AI as far and wide across the Paradigm as possible. To do this, they decided to split up and try different ways to get the message out. This caught the attention of the mysterious ShaDAO organization who locked Spice and her command out of TPL entirely.

Spice had to get access to the P.O.S.T. Box to get a message to Zinc. Then, CyberBrokers had to work with Ken and Zinc to try to get Spice and her command back into TPL.

CyberBrokers took the role of Mission Command during Ken and Zinc’s heroic infiltration of a ShaDAO building. Decisions made by players led to a path where only Zinc escaped and Ken was captured by ShaDAO.


---

# 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://docs.cyberbrokers.com/user-guide/missions/alpha/qa-m03/summary.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.