> For the complete documentation index, see [llms.txt](https://docs.scoutradar.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scoutradar.xyz/sounds-and-new-cards.md).

# Sounds and new cards

Each lane can play a short cue when a new card enters it. Pick the sound in the lane's `Filters` panel under **Sound on new card**: Ping, Chime, Horn, Radar, or Off. Clicking a sound previews it and saves it at once; no `Apply` needed.

## When a lane plays its sound

A lane plays its sound when a card **enters the lane** — the moment the lane's filters first hold for that token — and that moment is less than a minute old. The same rule draws the **green rail** on the card's left edge, so a sound always corresponds to a card you can see at the top of a lane sorted by Newest.

Examples:

| Lane filters         | What triggers the sound                                                                                                                  |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| none (All signals)   | A token arrives on the board — the first scout bought it.                                                                                |
| Scouts ≥ 10          | The **10th scout** buys. The token may have been on the board for hours; for this lane it is new now.                                    |
| Crews ≥ 3            | The third independent crew buys.                                                                                                         |
| Vol at signal ≥ $50k | A token arrives on the board with that much volume in its signal minute (the value is fixed at the signal, so the entry is the arrival). |

What does **not** trigger a sound:

* A card that starts passing a filter because a **live** value drifted (market cap entering an `MC now` range).
* Old cards that a **widened filter** lets in — their entry moment is old.
* A card whose entry moment is more than a minute old when your browser first sees it (for example right after you open the page: the board loads silently).
* A token that leaves a lane and comes back under the same conditions — one sound per entry moment.

## One sound per moment, not per lane

If two lanes qualify the same card at the same instant (say, both have no thresholds), you hear **one** cue, from the leftmost lane whose sound is on. If they qualify it at different moments — All signals at arrival, Runners when the 10th scout buys — you hear both, at different times. A lane set to Off never silences another lane.

## The green rail

The green left edge marks a card whose entry into **this lane** is less than a minute old. The same card can carry the rail in one lane and not in another: in Runners it is new when the 10th scout buys; in All signals it stopped being new an hour ago.

## Why you may hear nothing at first

Browsers block audio until you interact with the page. Click anywhere on the board once, and sounds work from then on. The small toast at the bottom lists every sound the page played, with the lane and the token, so you can always check what you heard.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scoutradar.xyz/sounds-and-new-cards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.