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

# Terminology

> Every term the Pome docs use — digital twin, task, examinee, coach, judge, run, score — defined in one place.

Every coined term in these docs, defined once. Linked pages go deeper.

| Term                   | Definition                                                                                                                                                                                                                                        |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Digital twin**       | A deterministic simulation of a real SaaS API (GitHub, Slack, Stripe, Gmail, Linear). Same request/response shapes and error semantics as the live service, no production side effects. See [How Pome works](/docs/how-pome-works#digital-twins). |
| **Task**               | The exam: a markdown file with a seed state, a prompt, and acceptance criteria. See [Tasks](/docs/how-pome-works#tasks).                                                                                                                          |
| **Seed state**         | JSON the digital twin loads before the agent starts — the initial world (repos, channels, charges).                                                                                                                                               |
| **Examinee**           | The clone of the agent under test. It works the task against the twins and never sees the grading criteria.                                                                                                                                       |
| **Coach**              | The agent driving the test (for example, your Claude Code session over the Pome MCP). It installs, launches runs, finalizes, and reads reports. The coach can see criteria; the examinee cannot.                                                  |
| **Judge**              | Pome's scorer. It evaluates the recorded trace against the task's criteria and produces the 0–100 score.                                                                                                                                          |
| **Run**                | One execution of a task by one agent: boot the twin with the seed, record every call, score the result. Artifacts land in `runs/<task>/<run-id>/` and on the [dashboard](/docs/dashboard).                                                        |
| **Twin session**       | The live, isolated twin instance a run talks to. It expires; finalize the run while the session is still live, or it cannot be scored.                                                                                                            |
| **Finalize**           | The call (`finalize_run`) that closes a run and triggers scoring.                                                                                                                                                                                 |
| **Criteria**           | A task's acceptance checks. `[code]` criteria are deterministic checks on twin state or events; `[model]` criteria are judgment checks read by the LLM judge.                                                                                     |
| **Score**              | 0–100 aggregate satisfaction across criteria. A run passes when the score meets the task's `passThreshold` (default 100).                                                                                                                         |
| **Trace**              | The recorded stream of everything the examinee did (`events.jsonl`): twin HTTP calls, LLM calls, run lifecycle events.                                                                                                                            |
| **Surface**            | A place you drive the loop from: CLI, Agent Skill, MCP, or dashboard. See [Which surface?](/docs/which-surface).                                                                                                                                  |
| **`pome.config.json`** | The manifest that connects a repo to Pome: the agent's slug, its start command, and the twins it uses. Written by `pome init`, read by every run. See [Connect your agent](/existing-agent).                                                      |