> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/synthesis/navigate-synthesis-outputs/manuscript-in-synthesis.md).

# Manuscript in Synthesis

Learn how to navigate the Manuscript page in Synthesis.

A Manuscript is a full written report of the review — similar in structure to a published journal article, with sections, references, and tables — that a reviewer has drafted to walk you through their findings in prose rather than diagrams. This page shows exactly what they've written, kept current as their review progresses.

### What You Can Do Here

* **Navigate by section** — select **Show Table of Contents** to open a navigable outline, generated automatically from the document's headings.
* **View references** — open the **References** panel at the bottom of the page for the full reference list, or select any blue in-text citation to jump straight to its entry.
* **Download** the whole document as a Word file, via the three-dot menu.

This page is read-only.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FphbBrInbfurqLbrmJTl8%2Fmanuscript%20on%20synthesis.png?alt=media&amp;token=2f2c29a4-7c27-4501-a1b6-986c4380a577" alt="The Manuscript page in Synthesis, showing the document content and its table of contents"><figcaption><p>The Manuscript page shows your review as a written report.</p></figcaption></figure>

### Filters

Filters that apply elsewhere in Synthesis (see [Filters on Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/filters-on-synthesis.md)) do not apply here — the Manuscript is already written to reflect exactly what its author intended, so a separate filtering layer isn't offered on top of it.

### FAQs

<details>

<summary>Was this written by AI or by a person?</summary>

Manuscript content is written manually by the reviewer in what they call Manuscript Editor — it isn't automatically generated.

</details>

<details>

<summary>Why is there no filter option here?</summary>

Manuscript and Dashboard are the two Synthesis pages that filters don't apply to — see [Filters on Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/filters-on-synthesis.md) for why.

</details>

<details>

<summary>Do I need an account to read this?</summary>

No — if you've been sent a link, you can read and download this document without signing up.

</details>

### Next Steps

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-file-lines">:file-lines:</i><br><strong>Manuscript Editor</strong></td><td>Draft or edit the content shown here.</td><td><a href="/review-workflow/synthesis/set-up-synthesis-outputs/manuscript-editor.md">Manuscript Editor</a></td></tr><tr><td><i class="fa-sliders">:sliders:</i><br><strong>Filters on Synthesis</strong></td><td>Learn where Synthesis-wide filters apply.</td><td><a href="/review-workflow/synthesis/navigate-synthesis-outputs/filters-on-synthesis.md">Filters on Synthesis</a></td></tr></tbody></table>


---

# 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.nested-knowledge.com/review-workflow/synthesis/navigate-synthesis-outputs/manuscript-in-synthesis.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.
