> 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-1.md).

# See the signal between sessions

Follow the evidence. Share a view. Find your people.

**US EQUITIES + REALITY RTOKENS**

## Join the research desk

Sign in to publish notes, reply, like, repost, quote, and message other members.

<a href="/see-the-signal-between-sessions-11.md" class="button primary">Sign in to Tidelight ↗</a>

## Research in conversation

### The desk feed

**For your desk** · Latest

Search public research. Searches notes currently loaded on this page.

{% hint style="info" %}
**The desk is quiet for now.**

Start with a source-backed note on a listed US issuer or a Reality rToken. Your activity will shape the feed over time.
{% endhint %}

## Find a research voice

View profile ↗

## Built around what you follow

Notes linked to issuer events, SEC filings, and Reality pairs surface closer to the top as you research and react.

1. **Watchlist focus**
2. **Research trail**
3. **Helpful reactions**
4. **Fresh evidence**

<a href="/see-the-signal-between-sessions-7.md" class="button secondary">Tune your watchlist ↗</a>

## Take the conversation further

Compare a source or a scenario in a private conversation with another researcher.

<a href="/see-the-signal-between-sessions-14.md" class="button secondary">Open messages ↗</a>

## Community standard

Separate issuer facts from token-market claims. Be clear about uncertainty. No trade calls, promotion spam, or unsupported claims.

Messages are limited to conversation participants; public notes stay readable to guests.


---

# 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-1.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.