> 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/cha-kan-hui-hua-zhi-jian-de-xin-hao-10.md).

# 查看会话之间的信号

查看已配置了哪些公开数据和研究服务、“新鲜度”的含义，以及决策轨迹保存在哪里。

{% hint style="info" %}
**仅限纸面研究。** Tidelight 不会发送任何交易所订单。
{% endhint %}

## 了解交易台能看到什么。

提供方配置和公开市场新鲜度，由此部署进行检查。

### Bitget 公开市场

**需要设置**

正在检查市场数据流……当前没有数据流快照

会话元数据：检查中 · 发行方元数据：检查中

### Qwen 研究综合

**需要设置**

仅检查密钥是否存在；已配置的密钥并不能证明上游可用。

### Supabase 身份与存储

**需要设置**

连接设置已存在。已登录的私有工作流提供经过身份验证的健康检查。

### Nightwatch 定时运行器

**需要设置**

仅为配置；已安排为每天 UTC 09:00 运行（Hobby 方案可能会在 09:00–09:59 之间启动）。此检查并不能证明 cron 运行成功。每次运行都会在 Postgres 中重新检查是否选择启用以及是否暂停。

部署待定 · 请求 — 毫秒 · 请求 ID `待定`

已检查等待中 · 每 30 秒刷新一次

## 每个数据流都有自己的时钟。

在提供方新鲜度窗口之后，市场快照会被视为过期。如果 Bitget 不可用，市场页面会显示不可用状态，而不会替换为示例价格。

[打开实时市场图 ↗](/untitled-zh/cha-kan-hui-hua-zhi-jian-de-xin-hao-3.md)

## 运行会保留其输入。

研究笔记会保留其证据和引用。策略运行会保留已完成的蜡烛快照、假设以及 SHA-256 指纹。Nightwatch 的决策会记录到已登录账户的私有纸面账本中。

[查看已保存的研究 ↗](/untitled-zh/cha-kan-hui-hua-zhi-jian-de-xin-hao-9.md)

## 尚未声明的内容。

此视图不证明数据库恢复、提供方 SLA、外部安全审计或底层发行方会话对齐。那些需要经过实测的运维演练和独立审查。

[查看产品证据地图 ↗](/untitled-zh/cha-kan-hui-hua-zhi-jian-de-xin-hao-13.md)


---

# 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/cha-kan-hui-hua-zhi-jian-de-xin-hao-10.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.