Glossary
Context Engineering Glossary for Agent Teams
A plain-language glossary for agent teams covering context engineering terms that directly affect orchestration, retrieval, and pSEO quality.
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.
Agent orchestration
Playbooks for deciding when to stay single-agent, when to split work, and how to keep retrieval surfaces readable by both humans and bots.
Pain points
- Teams copy the same markdown into dozens of pages and call it pSEO.
- Index coverage drops because archive, helper, and low-value URLs outnumber the useful ones.
Expected outcomes
- Higher-value detail pages with clearer intent and better bot retrieval.
- Cleaner index coverage because only curated hubs and utility pages are generated.
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.
Related articles
Eight Hooks That Guarantee AI Agent Reliability
CLAUDE.md rules get followed about 80% of the time. Hooks get followed 100% of the time. After six months of testing, these are the eight I never removed.
Claude Code in 2026: Layers Matter More Than Tools
I installed three popular Claude Code extensions and productivity barely moved. The problem was never which tools to pick.
Why Your Codex Config Isn't Working: The .codex/ Folder Problem
I edited config.toml, wrote rules in AGENTS.md, and nothing stuck. Turns out the folder structure itself was the issue, not my settings.
Author
Tony Lee / 이정민Tony Lee (이정민, 토니리) writes these resources as an AI engineer, solo builder, and founder focused on SEO, AEO, AI agents, and startup execution.
Summary
Use this as a shared vocabulary before you split work across agents, pages, or retrieval surfaces.