---
title: "Use Reference"
url: "https://docs.caracal.run/v1.0/reference/"
markdown_url: "https://docs.caracal.run/markdown/v1.0/reference.md"
description: "Search exact Caracal terms, configuration, limits, errors, compatibility, release surfaces, and wire contracts."
page_type: "landing"
concepts: []
requires: []
---

# Use Reference

Canonical URL: https://docs.caracal.run/v1.0/reference/
Markdown URL: https://docs.caracal.run/markdown/v1.0/reference.md
Description: Search exact Caracal terms, configuration, limits, errors, compatibility, release surfaces, and wire contracts.
Page type: landing
Concepts: none
Requires: none

---

Use Reference when you need an exact value or contract. Use [Guides](/v1.0/guides/) for procedures and [API Reference](/v1.0/api/) for endpoint behavior.

## Find the Canonical Answer

| Question                                                 | Canonical page                                           |
| -------------------------------------------------------- | -------------------------------------------------------- |
| What does this public term mean?                         | [Glossary](/v1.0/reference/glossary/)                         |
| Why did this request fail?                               | [Error Codes](/v1.0/reference/errors/)                        |
| Which setting controls this behavior?                    | [Configuration Keys](/v1.0/reference/configuration/)          |
| Which configuration source wins?                         | [Configuration Order](/v1.0/reference/config-precedence/)     |
| What is the current default or limit?                    | [Defaults and Limits](/v1.0/reference/defaults-and-limits/)   |
| What exit status does automation receive?                | [CLI Exit Codes](/v1.0/reference/runtime-exit-codes/)         |
| Which runtimes and version combinations are supported?   | [Compatibility](/v1.0/reference/compatibility/)               |
| Which packages and images belong to one release?         | [Release Map](/v1.0/reference/release-package-runtime-map/)   |
| Which bytes and JSON fields are interoperable?           | [Wire Contracts](/v1.0/reference/interoperability-contracts/) |
| How do I answer a likely product or operations question? | [FAQ](/v1.0/reference/faq/)                                   |

## Read Values by Layer

* **Product language** is the terminology shown in the web console and SDK facades.
* **Runtime configuration** controls the CLI, SDK loaders, and deployed services.
* **Protocol behavior** covers HTTP fields, raw JWT claims, status codes, and schemas.
* **Release behavior** covers SemVer, package lockstep, images, and documentation versions.

Do not substitute a protocol name for its public product term. Public surfaces use **Session ID** and **Delegation ID** while raw Coordinator and JWT contracts retain fields such as `agent_session_id` and `delegation_edge_id`.

## Source of Truth

Code, package manifests, deployment configuration, and checked-in schemas are authoritative. This section explains those sources; it does not create a second contract.

## Next Step

Search [FAQ](/v1.0/reference/faq/) for a question, or open [Glossary](/v1.0/reference/glossary/) before naming a product concept in code or documentation.