# Reference

> Exact values and lookup tables — terminology, entity relationships, statuses, permissions, limits, and calculations. Compact pages built for retrieval, not reading order.

_Status: Reviewed — human-edited, facts not yet confirmed against the product._

Reference pages hold the exact values the rest of the site points to. Each page is a set of
tables meant to be retrieved on its own — by a person checking one value or by an agent
grounding a claim.

- [Terminology](/reference/terminology) — every product noun, its synonyms, and its one canonical definition
- [Entity relationships](/reference/entity-relationships) — which object contains, uses, or references which
- [Lifecycle diagrams](/reference/lifecycle-diagrams) — contact status, sequence toggle, and email validation lifecycles as text diagrams
- [Statuses](/reference/statuses) — contact statuses, stages, toggle colors, validation results, and inbox categories
- [Permissions and roles](/reference/permissions) — organization, team-wide, and workspace roles with their permission lists
- [Limits](/reference/limits) — sending, rate, and plan limits
- [Calculations](/reference/calculations) — how each reported number is computed

## Planned

Reference pages specified but not yet written:

| Page | Status |
| --- | --- |
| Status transitions (full matrix) | Not written |
| Feature availability by plan | Not written |
| Channel availability | Not written |
| Data retention | Not written |
| Timezones and date behavior | Not written |
| Naming conventions | Not written |

## Related

- [Specifications](/specifications) — the objects these values belong to
- [Behavior](/behavior) — the logic that moves objects between these statuses

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) — the field-level source of truth for every value here
- Machine spec: [bundled.yaml](https://docs.reply.io/api-reference/bundled.yaml)