> 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/untitled-zh/yan-jiu-liu-cheng.md).

# 研究流程

遵循每一步。

提出一个关于美股或其代币化市场的问题。Tidelight 会核查最新证据，梳理可用工具，测试一个场景，并且只有在其门槛一致时才提供交易分析。

你的市场问题

开始研究 ↗

**试着提一个问题**

* 你怎么看 NVDA 和 TSLA？
* 根据最新消息比较 Apple 和 Microsoft
* rNVDA 市场值得审视吗？

事件 · 证据 · 风险敞口 · 决策


---

# 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/untitled-zh/yan-jiu-liu-cheng.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.