> For the complete documentation index, see [llms.txt](https://acma.gitbook.io/acmc-cookbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://acma.gitbook.io/acmc-cookbook/reviewing.md).

# Reviewing Submissions

* Submissions to ACMC are generally reviewed by (at least) two members of the computer music / music tech community.
* Reviewing is normally single-blind (reviewer is anonymous to the submitter, but the reviewer can see the submitter's identity).
* Reviews are normally of the **abstract** (not full papers) for papers and artist talks.

In the past, ACMC has used EasyChair to run reviewing and we found (2020) that the free tier was sufficient for organising the conference. EasyChair can be tricky to understand, but it's only bad compared to all the other conference management systems out their :-)

In 2021 Vince Giles created his own reviewing system with Microsoft Forms and Excel which seemed to work ok.


---

# 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://acma.gitbook.io/acmc-cookbook/reviewing.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.