Glossary

The Glossary is your business dictionary—a structured collection of acronyms, jargon, and domain-specific terms that your organization uses.

Overview

Glossary nodes provide quick, concise definitions for business terms and acronyms. They're used by both the Head (agent brain) and Hands (task executors) to understand the language your team uses.

When to Use Glossary

Use Glossary context when you need to:

  • Define acronyms (ARR, CAC, MQL, etc.)

  • Explain industry jargon or technical terms

  • Provide quick reference definitions

  • Standardize terminology across teams

  • Translate between business and technical terms

Fields

Field
Required
Description

type

Required

Must be glossary

domain

Required

Which domain(s) this applies to: "*", "marketing", etc.

Glossary Format

Glossary entries use a structured YAML format:

Examples

Example 1: Company-Wide Glossary

Example 2: Marketing Glossary

Example 3: Finance Glossary

Example 4: Product/Engineering Glossary

Example 5: Sales Glossary

Glossary vs Knowledge

The key difference between Glossary and Knowledge is depth and format:

Glossary
Knowledge

Structured YAML format

Free-form Markdown

Short, dictionary-style definitions

Rich, detailed explanations

One or two sentences

Multiple paragraphs

Term + description

Context, examples, rules

When to Use Glossary

Use Glossary for:

  • Simple acronym expansions

  • Quick term lookups

  • Standardizing vocabulary

  • Terms that need only a sentence or two

Example:

When to Use Knowledge

Use Knowledge for:

  • Detailed explanations

  • Business rules and context

  • Multi-paragraph documentation

  • Examples and edge cases

Example:

Best Practices

Keep Definitions Concise

circle-check

Be Domain-Specific When Needed

The same acronym can mean different things in different domains:

Marketing ARR:

Finance ARR:

Avoid Circular Definitions

circle-check

Include Units or Thresholds

When relevant, specify units or thresholds:

Standardize Across Teams

Use the company-wide glossary (domain: "*") for terms that should mean the same thing everywhere:

Organizing Large Glossaries

For organizations with many terms, consider organizing by domain:

Structure:

  • context/glossary-company.md - Company-wide terms

  • context/glossary-marketing.md - Marketing-specific terms

  • context/glossary-finance.md - Finance-specific terms

  • context/glossary-product.md - Product-specific terms

  • context/glossary-sales.md - Sales-specific terms

This makes glossaries easier to maintain and update.

Common Pitfalls

Don't Mix Glossary with Instructions

triangle-exclamation

Don't Use Glossary for Long Explanations

If your description is more than 2-3 sentences, use Knowledge instead.

Don't Forget to Update

Glossaries become stale. Review and update regularly:

  • When business processes change

  • When new products launch

  • When teams adopt new terminology

  • At least quarterly

See Also

Last updated