> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/reference/glossary.md).

# Glossary

* **Audience Under Management (AUM)** — the accounts and contacts the always-on system actively manages.
* **Credits** — the unit of usage; each plan includes a monthly allotment.
* **Decision Trace** — the record of why an action happened, joined by trace ID.
* **FIRE score** — Fit, Intent, Recency, Engagement, combined into a Hot / Warm / Cool tier.
* **Harness** — the orchestrator that reasons over Intelligence and runs the loop.
* **Identity Graph** — the resolution that ties events to real people and accounts.
* **Intelligence** — what the system knows: context and memory.
* **Master goal** — one of six standing focuses you choose.
* **Target** — a specific, time-bound objective under a master goal.
* **trace ID** — the key stamped at origin and carried through every step, so events, decisions, and outcomes can be joined.
* **Visitor reveal** — turning anonymous site traffic into named accounts and contacts (Pro and higher).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aloop.icustomer.ai/reference/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.