> For the complete documentation index, see [llms.txt](https://docs.tidelight.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tidelight.app/use-tidelight/research-desk.md).

# Research desk

Build source-based briefs you can inspect.

## Research desk

A research brief makes the reasoning visible from the first question onward.

### The research flow

1. **Event** — Define the news, claim, or question.
2. **Evidence** — Attach a source and review claims against captured text.
3. **Exposure** — Identify relevant issuers, sectors, and tokenized assets.
4. **Scenario** — Consider catalysts, opposing evidence, and invalidation conditions.
5. **Decision** — Keep the record for your own judgment.

### Add sources carefully

Mini supports HTTPS sources from the selected company, SEC.gov, and supported public publishers. Tidelight shows source links and applies collection limits.

Pro can compare up to five excerpts that you provide. It retains those excerpts with their source links.

{% hint style="warning" %}
Always read the original source. External articles may be incomplete, inaccurate, or out of date.
{% endhint %}

### Read a brief

Open each evidence card to inspect its source date and supporting text. Treat confidence as context, not certainty. Review counter-evidence before forming a view.


---

# 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.tidelight.app/use-tidelight/research-desk.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.