> For the complete documentation index, see [llms.txt](https://strategy.extinctionrebellion.be/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://strategy.extinctionrebellion.be/strategy-2020/feedback-from-the-rebels/process-how-did-we-write-this-text.md).

# Process - how did we write this text?

This document is based on a discussion held at the XR retreat 28-30 august 2020 in Solre-Saint-Géry and the online experimental activist assembly on 29 august. 

This text is a proposal about what XR Belgium should focus its strengths on in the coming half year. It will be presented formally to local groups and national coordinators, who will discuss the proposal autonomously and give feedback. 

To participate in the feedback process, please join the sessions organised by the national circles or the local groups. You can find the list of feedback discussion meetings of the local groups and national circles on [**this page**](https://strategy.extinctionrebellion.be/local-feedback-sessions). 

We aim to have a final text ready by 28 September, followed by a national assembly to validate the strategy.


---

# 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://strategy.extinctionrebellion.be/strategy-2020/feedback-from-the-rebels/process-how-did-we-write-this-text.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.