> 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/see-the-signal-between-sessions-10.md). # See the signal between sessions See which public data and research services are configured, what freshness means, and where the decision trail is preserved. {% hint style="info" %} **Paper research only.** No exchange orders are sent by Tidelight. {% endhint %} ## Know what the desk can see. Provider configuration and public market freshness, checked from this deployment. ### Bitget public markets **Setup required** Checking market feed… No current feed snapshot Session metadata: checking · issuer metadata: checking ### Qwen research synthesis **Setup required** Key presence only; a configured key does not prove upstream availability. ### Supabase identity & storage **Setup required** Connection settings are present. Signed-in private workflows provide the authenticated health check. ### Nightwatch scheduled runner **Setup required** Configuration only; scheduled for 09:00 UTC daily (Hobby may start it during 09:00–09:59). This check does not prove a cron run succeeded. Each run rechecks opt-in and pause in Postgres. Deploy pending · request — ms · request ID `pending` Checked waiting · refreshes every 30 seconds ## Every feed has a clock. Market snapshots are treated as stale after the provider freshness window. If Bitget is unavailable, market pages show an unavailable state instead of substituting sample prices. [Open the live market map ↗](/see-the-signal-between-sessions-3.md) ## Runs keep their inputs. Research notes retain their evidence and quotes. Strategy runs keep completed candle snapshots, assumptions, and a SHA-256 fingerprint. Nightwatch decisions are recorded to the signed-in account’s private paper ledger. [Review saved research ↗](/see-the-signal-between-sessions-9.md) ## What is not claimed yet. This view does not certify a database restore, provider SLA, external security audit, or underlying-issuer session alignment. Those require measured operational rehearsals and independent review. [See the product evidence map ↗](/see-the-signal-between-sessions-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/see-the-signal-between-sessions-10.md?ask=&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.