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

# See the signal between sessions

## One event.

A decision you can inspect.

Follow the evidence from the first question to a guarded paper decision. Each step links to a working product surface and leaves the next action with the researcher.

**See the signal between sessions.** Three hackathon tracks, one traceable workflow.

{% stepper %}
{% step %}

### Start with an event

**AI TRADING DESK**

Frame a company or market question. Supply supported public sources or paste passages in Pro, then inspect every displayed claim beside its matched quote.

[Open Research Desk ↗](/see-the-signal-between-sessions.md)
{% endstep %}

{% step %}

### Map the exposure

**TOKENIZED EQUITIES**

Review the linked Bitget Reality instrument, public market mark, freshness, and upside, downside, and invalidation scenarios. Choose whether to replay or monitor it.

[Explore Market Map ↗](/see-the-signal-between-sessions-3.md)
{% endstep %}

{% step %}

### Challenge the rule

**ALPHA FACTORY**

Run deterministic SMA research on completed public candles. Inspect the fixed holdout, rolling windows, cost stress, trades, and exact input fingerprint. Negative results stay visible.

[Open Strategy Lab ↗](/see-the-signal-between-sessions-4.md)
{% endstep %}

{% step %}

### Observe in a paper ledger

**AGENTIC TRADING**

Nightwatch supports manual checks and an opt-in daily scheduled check on one Reality market. It records the decision and market snapshot, applies database-enforced limits before simulated fills, and remains pauseable by the account owner.

[Open Nightwatch ↗](/see-the-signal-between-sessions-8.md)
{% endstep %}
{% endstepper %}

## Small, explicit trust boundaries.

Public Bitget endpoints provide market data. Server-side Qwen synthesis receives bounded source text. Supabase stores signed-in user records under row-level policies. The browser never receives provider secrets. Nightwatch is paper-only; Hobby deployments run the scheduled check once daily.

**Researcher**\
Question · selected sources · explicit handoffs

*↓*

**Tidelight application**\
Quote checks · deterministic backtests · paper guardrails

*↓*

**Providers & private ledger**\
Bitget public feed · Qwen server key · Supabase owner-scoped data

### 01 / RESEARCH — What can be checked now

Captured excerpts, quote-matched claims, source URLs, retrieval timestamps, and counter-evidence found in submitted passages.

### 02 / VALIDATION — What can be reproduced

Completed candle arrays, deterministic SMA 20/50 logic, explicit fee and slippage assumptions, windows, and hashes.

### 03 / PAPER AGENT — What remains deliberately bounded

Manual or once-daily opt-in checks, private audit records, stale-feed rejection, position and daily limits, and no live exchange execution.

{% hint style="info" %}
Research quality, provider availability, and simulated strategy outcomes depend on the captured inputs. This walkthrough does not claim audited alpha, a provider SLA, institutional certification, or investment advice.
{% endhint %}

## Bring a question. Keep the evidence.

[Open Research Desk ↗](/see-the-signal-between-sessions.md)

[Read the usage guide →](/start-here.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-13.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.