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

# GLOSSARY.yml (domain)

A domain's vocabulary file. It merges with the [root `GLOSSARY.yml`](/concepts/glossary.md), with the domain winning when a term collides.

## What it is

The shared definition of what `GLOSSARY.yml` is — its role, its entry format, and when a term should be a [skill](/concepts/skill.md) instead — lives on the [root `GLOSSARY.yml`](/concepts/glossary.md) page. This page covers only the **scope behavior** at the domain level.

A domain glossary holds the terms this team uses, and overrides any root term whose meaning differs for this audience.

## Where it lives

Optionally, one per domain:

```
.lynk/domains/<domain>/GLOSSARY.yml
```

## Format

Same entry format as the root — key → `name` / `description`. See [GLOSSARY.yml → Format](/concepts/glossary.md#format).

**Composition merges across scopes.** The effective glossary in a domain is the root glossary merged with the domain's. On a key collision, the **domain entry wins** — this is how a team gives a company-wide term its own meaning. Terms the domain doesn't redefine are inherited from the root unchanged.

## Examples

**One domain-specific term.**

```yaml
mql:
  name: MQL
  description: Marketing Qualified Lead. A lead that has met the marketing team's engagement-score threshold and is ready to pass to sales.
```

**Overriding a shared term for this audience.** The root defines `lead` broadly; marketing narrows it.

```yaml
lead:
  name: Lead
  description: A marketing-qualified lead — narrower than the company-wide definition. Excludes self-serve signups, which marketing does not source.

cac:
  name: CAC
  description: Customer Acquisition Cost. Total marketing and sales spend in a period divided by new customers acquired in that period.
```

## Validation

* Optional; a domain with no glossary inherits the root vocabulary.
* Each entry declares `name` and `description`.
* A root/domain key collision resolves to the domain entry (expected, not an error).

## Related

* [GLOSSARY.yml](/concepts/glossary.md) — the root concept and the shared definition
* [Domain](/concepts/domain.md) — the agent this vocabulary belongs to
* [Domain LYNK.md](/concepts/domain/lynk-md.md) — the team's orientation


---

# 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.getlynk.ai/concepts/domain/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.