> 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 The full reference, A to Z. For the short version in loop order, see the [Getting Started glossary](/getting-started/glossary.md). | Term | Meaning | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ABC Card** | Audience, Brand & Competition: the picture the system builds of your business from your domain, which you confirm or correct during onboarding. Your confirmation turns it into working context. | | **Activation** | What a play's run delivers into a destination: the live push of an audience to a channel like LinkedIn, Instantly, or your CRM. One play can produce many activations. (On the sales side, "activation" can also mean a user starting to use a product. In these docs it always means the platform object.) | | **Agent** | A specialized worker iHarness coordinates behind the scenes, each covering one part of the loop. You see agents as bylines on the work they deliver. See the [Agent catalog](/reference/agent-catalog.md). | | **Cohort** | A named group of accounts or contacts under a segment, defined by a shared trait or behavior. Cohorts are what you build, monitor, and activate. | | **Credits** | The single unit of usage every plan includes. The system draws credits as it works, and your balance shows in the top bar. | | **Decision** | A moment where iHarness chose one option over others, spent something finite doing it, and said what it expected to happen. The unit of work. Anything without all three is a step. | | **Decision trace** | The receipt for a decision: why it was made, on what evidence, under what authority, and what came of it. | | **FIRE score** | Fit, Intent, Recency, and Engagement, combined into a tier so you know who is worth acting on right now. See [FIRE scoring](/audience/fire-scoring.md). | | **Goal** | One of six fixed go-to-market ambitions. Your standing focus, and goals never expire. | | **Growth Brain** | The self-learning context graph iHarness runs on: customer, company, and audience context, built on OneSource identity, accruing from every connected system and every decision outcome. iHarness's memory and the Growth Brain are the same thing. See [Context and memory](/concepts/context-and-memory.md). | | **iConnect** | The integrations layer: activation out, governed connection in. The only part of the platform that touches your systems. See [Your stack](/integrations/stack.md). | | **iHarness** | The agent running your growth loop. It reasons over your Growth Brain, decides what to do, and coordinates the agents, on request and on its own. It executes, within guardrails. | | **KPI** | What the business can actually read: a measurable number under a goal. If no connected source makes it readable, it is not a KPI for that workspace. | | **Learning** | The recorded difference between what a decision expected and what actually happened, so the next decision is better. | | **The loop** | The always-on cycle behind everything: capture what is happening, resolve who it is, score it, decide what to do, and attribute what came of it, then back to the top. | | **OneSource ID** | The immutable identity a verified match earns, and the foundation the Growth Brain is built on. Licensed third-party data enters only by resolving to a OneSource ID, and deletion requests propagate at the same level. | | **Outcome** | What happened, measured against what was expected. Outcomes move targets, and targets move KPIs. | | **Pixel** | The snippet on your site that reveals who is visiting and ties anonymous visits to real accounts. | | **Meta loop** | The slower loop underneath the 90-day loop: outcomes become evidence, and evidence sizes the next target. It runs across quarters and never closes. | | **Play** | A named, repeatable piece of work that moves a KPI: picked from the library, made yours for your workspace, and editable through the chat where it was created. Plays have runs. | | **Playbook** | Retired term, see Play. Some internal identifiers keep the historical name. | | **Pulse (the surface)** | Where the system raises its hand: the queue of things that need you to see or decide. **A pulse (an item)** is one such card. | | **Run** | One execution of a play. Each run delivers into an activation. | | **Segment** | The top-level split of your market: B2B or D2C. Cohorts live under segments. | | **Signal** | An event or behavior that tells the system something changed: a site visit, a demo request, a funding round. | | **Suppression** | The records a play must not touch: your exclusion lists, consent boundaries, and the one-cadence-per-contact rule. | | **Target** | An achievable, computed commitment: a number and a date under a goal, moved by outcomes. A number that cannot be reached is not a target. | | **Workspace** | Your environment: one company or brand, its data, team, and settings. | --- # 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=&goal= ``` `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.