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

# Glossary

> The words everydeck uses, in plain language: case, flow, run, expectation, change door, read bridge, outbox, version, Needs you, Fixed, Came back and more.

> **Agent key**
>
> A key for your coding agent, for one environment. It lets the agent report changes and pick up repairs. Valid for 30 days. See [Changes](https://docs.everydeck.ai/using/changes.md#reports-of-your-coding-agent).

> **App map**
>
> The file `everydeck/app-map.json` your coding agent writes during the setup: the tables, pages, flows, jobs and services of your app, each with its place in the code. You approve what everydeck derives from it. See [How setup works](https://docs.everydeck.ai/get-started/how-setup-works.md#the-app-map).

> **Approve**
>
> Your one click on the setup page. It allows what everydeck will see and do in your app. Later, new permissions ask again.

> **Case**
>
> A bundle of events of the same kind of problem, with a short address like `ACME-14`. It is a way of grouping work, not a proven cause. See [Cases and repairs](https://docs.everydeck.ai/using/cases-and-repairs.md).

> **Came back**
>
> A case your agent fixed or you marked as fixed, where the same error happened again in the reported or a later version. It opens again with the same address, and you get an email.

> **Change door**
>
> everydeck's own Edge Function in your Supabase project, `everydeck-write-door`. It makes the changes your team starts in everydeck, and only what you switched on. See [Changing data](https://docs.everydeck.ai/using/changing-data.md).

> **Data gap**
>
> A time in which everydeck is missing data, for example because the SDK dropped events at its limit. A data gap is not a failure. It means everydeck cannot judge.

> **Developer view**
>
> A switch that shows technical details next to the plain words on every page. See [Developer view](https://docs.everydeck.ai/using/developer-view.md).

> **Environment**
>
> Every app has two: development and production. Each has its own keys, data and cases. See [Going live](https://docs.everydeck.ai/developers/going-live.md).

> **Event**
>
> What your app sends to everydeck: errors, signals of flows, logs and breadcrumbs. Free includes 10,000 a month. Heartbeats, page loads, visits and sign-ins never count.

> **Expectation**
>
> A rule between two signals: after A, B must arrive within a set time. If B does not come, a case **Missed expectation** opens. See [Flows and journeys](https://docs.everydeck.ai/using/flows-and-journeys.md).

> **Fixed**
>
> The state of a case after your coding agent reported a fix, or after you clicked **Mark as fixed**. everydeck then watches. If the same error happens again, the case shows **Came back**.

> **Flow and run**
>
> "A flow is something your app does again and again; a run is one time it happened." For example signing in, creating a listing or paying.

> **Heartbeat**
>
> A small sign of life a part of your app sends every 5 minutes. Missing heartbeats are a monitoring gap, not an outage. See [App parts and heartbeats](https://docs.everydeck.ai/using/app-parts-and-heartbeats.md).

> **Hung**
>
> A run in which a request waited at least 30 seconds without an answer. Three such runs at the same place in 24 hours open a case **No answer**.

> **Manifest digest**
>
> A setting every SDK client sends. It names the approved version of your app map. Without it, everydeck refuses the data.

> **Monitoring gap**
>
> A case for something that went silent: no heartbeats, a job that did not report, or a flow that stopped sending after a new version. Not a confirmed outage.

> **Needs you**
>
> Your to-do list in everydeck: the cases and decisions that need a person. See [Needs you](https://docs.everydeck.ai/using/needs-you.md).

> **Open · watched**
>
> A new error that touches no flow with business consequences and few people so far. It shows on the Errors page only and becomes a task when it grows.

> **Outbox**
>
> For apps whose browser writes straight into the database. A trigger writes a short note in the same transaction, and a relay sends it to everydeck. So only confirmed results arrive. See [The outbox](https://docs.everydeck.ai/developers/going-live.md#the-outbox).

> **Part**
>
> One thing your app needs connected, like sign-in, payments or a scheduled job. The Setup page shows each part with its state. See [Setup page](https://docs.everydeck.ai/using/setup-page.md).

> **Probe run**
>
> The test events your coding agent sends during the setup. They count nowhere: no person, no case on the Errors page, no email.

> **Protocol**
>
> The log of who did what and when in everydeck, with before and after. Kept for 90 days on Free.

> **Read bridge**
>
> The connection through which everydeck reads your app's records. Your app opens it to everydeck, so everydeck never needs your app's address. It reads exactly what you approved. See [Your app's data](https://docs.everydeck.ai/using/your-data.md).

> **Reachability check**
>
> A call from outside to a public address of your app. Two failures in a row are a confirmed outage. See [Reachability checks](https://docs.everydeck.ai/using/reachability-checks.md).

> **Signal**
>
> A message from your app that a step of a flow happened, like "listing created". The role of the step in your app map decides how a run ends.

> **Source map**
>
> A file that maps your bundled browser code back to your source files, so errors show your own file and line. See [Source maps](https://docs.everydeck.ai/developers/source-maps-and-web-vitals.md).

> **Version (release)**
>
> One commit of your app, as your app reports it with every event. The SDK finds it by itself with the release key `auto`. See [Changes](https://docs.everydeck.ai/using/changes.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.