> ## Documentation Index
> Fetch the complete documentation index at: https://glassray.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Signals

> A signal is a piece of external feedback about a trace, step, or session - and a negative one can become a deviation.

A **signal** is one piece of external feedback about a [trace](/traces), a step, or a session: a thumbs-up/down, a star rating, or a written complaint. Signals let real-world feedback drive what Glassray investigates.

## Where signals come from

<CardGroup cols={2}>
  <Card title="Slack" icon="slack">
    Report a problem to the [Glassray bot](/slack) in a channel.
  </Card>

  <Card title="The dashboard" icon="user">
    A teammate flags a trace directly in Glassray.
  </Card>
</CardGroup>

A signal carries a **source** (`human`, `end_user`, `api`, `slack`, or `external`), an optional **valence** (`positive`, `negative`, or `neutral`), and optional `rating`, `body`, and `author`.

## What gets actioned

<Check>
  A **negative** signal pinned to a **resolved trace** is actioned: Glassray classifies that trace into a [flow](/flows) and appends it to a matching [deviation](/deviations), or logs a new **🔎 Suspected** one - a single report isn't yet confirmed to recur, so Glassray then scans for more examples to confirm it.
</Check>

Positive or neutral feedback, and feedback pinned only to a session or step (with no resolved trace), is stored for context but not actioned.

<Tip>
  Report misbehavior from [Slack](/slack) and Glassray turns it into a deviation.
</Tip>