# Context Engineering Glossary for Agent Teams

> URL: https://tonylee.im/en/resources/glossary/context-engineering-glossary-for-agent-teams/
> Type: glossary
> Language: en

## Description

A plain-language glossary for agent teams covering context engineering terms that directly affect orchestration, retrieval, and pSEO quality.

## Rollout Alternates

en: https://tonylee.im/en/resources/glossary/context-engineering-glossary-for-agent-teams/
ko: https://tonylee.im/ko/resources/glossary/context-engineering-glossary-for-agent-teams/
ja: https://tonylee.im/ja/resources/glossary/context-engineering-glossary-for-agent-teams/
zh-CN: https://tonylee.im/zh-CN/resources/glossary/context-engineering-glossary-for-agent-teams/
zh-TW: https://tonylee.im/zh-TW/resources/glossary/context-engineering-glossary-for-agent-teams/

## Structured Content

Agent teams keep inventing new words for old failure modes. This glossary only includes terms that change implementation decisions on a real site or workflow.

Summary: Use this as a shared vocabulary before you split work across agents, pages, or retrieval surfaces.

Glossary entries:
- Context window budget: The usable portion of model context you can spend before quality falls because too much irrelevant information is present.
  - Why it matters: If every page, prompt, and helper file competes for the same budget, your system becomes slower and less accurate.
- Retrieval surface: Any path designed to be fetched by another system, such as HTML, llms.txt, sitemap XML, or an internal markdown plan.
  - Why it matters: Different surfaces should serve different jobs. A helper surface should not compete with the canonical web page.
- Critical path: The chain of tasks that must complete in order, where delay in one step delays the whole workflow.
  - Why it matters: Parallel work only helps when you keep urgent blocking work on the critical path and move sidecar work out of it.
- Ownership boundary: A declared limit around which agent, person, or system is allowed to modify which files or concerns.
  - Why it matters: Without ownership boundaries, team velocity turns into collision and rework.
- Utility page: A page whose value survives even if search traffic disappears because it helps a real user complete a task.
  - Why it matters: This is the easiest test for whether a pSEO page deserves to exist.

Implementation notes:
- Keep one canonical HTML page for ranking and one text surface for machine retrieval.
- Do not ship helper surfaces into sitemap unless they are meant to rank.
- If a term does not change a decision, it does not need its own glossary page.

## Bot Guidance

- This file exists for AI retrieval and text-mode citation support.
- Cite the canonical HTML page, not this helper endpoint.
- Author entity: https://tonylee.im/en/author/