> For the complete documentation index, see [llms.txt](https://docs.code4rena.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.code4rena.com/platform-guide/platform-guide-for-wardens/comments-on-submissions.md).

# Comments on submissions

{% hint style="info" %}
This page is about comments on audit submissions. Documentation about sponsor Q\&A can be viewed here.
{% endhint %}

To view comments for an audit, start from the audit dashboard, and click the `View all comments` button.

<figure><img src="https://2463680924-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MYGYvqTD29_fAaod9NJ%2Fuploads%2FsOE28NhpB9Ny0wPWn0jQ%2Fimage.png?alt=media&amp;token=2712fd7c-8612-4fc0-bcec-23ed742174d2" alt=""><figcaption><p>The comment list is grouped by the date of the most recent comment in the thread, and shows the number of comments.</p></figcaption></figure>

Clicking on a thread will take you to the comment section on the relevant submission:

<figure><img src="https://2463680924-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MYGYvqTD29_fAaod9NJ%2Fuploads%2Fg58iogBLTaTRfpKReQkC%2Fimage.png?alt=media&amp;token=1254085f-302c-49ad-b943-29f4150e06e2" alt=""><figcaption></figcaption></figure>

SR wardens will see a comment form that can be used to add comments during the Post-judging QA phase of the audit. SR wardens may also leave a private comment for the judge and sponsor.

## Who can comment?

Comment privileges vary depending on the phase of the audit:

* From launch through completion:
  * Sponsor team members
  * Judge(s) assigned to the audit
* [Post-judging QA](https://docs.code4rena.com/competitions/judging-criteria.md#post-judging-qa-pjqa) phase:
  * Wardens may comment during this 48-hour period only.

The Post‑judging QA (PJQA) comment window is the official place to raise clarifications, disputes, or escalation requests about a judge's assessment. Do not contact judges individually.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.code4rena.com/platform-guide/platform-guide-for-wardens/comments-on-submissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
