Team AI Glossary
Key terms in team AI coordination, AI productivity, and knowledge management — coined and documented by Evols AI.
Jump to
Handoff Tax
The productivity cost incurred when context built in one AI session cannot transfer to the next person or role. Every handoff — developer to QA, sprint to sprint, engineer to engineer — requires expensive context reconstruction from scratch. Named and documented by Evols AI in 2026.
→The Handoff Tax: Why Your Team's AI Productivity Numbers Are WrongAI Coordination Tax
The compounding overhead that accumulates when multiple teammates use AI tools independently with no shared state between their sessions. Takes three main forms: duplicate AI investigations, context loss at handoff, and synchronization overhead disguised as code review latency.
→The Hidden Coordination Tax of Async AI WorkCold Start Problem (AI Onboarding)
The gap experienced by new teammates who must rebuild organizational context from scratch even in AI-native teams. AI tools transfer generic knowledge (from training data) but not organizational knowledge: past decisions, failed approaches, and codebase-specific constraints. A team knowledge layer is required to close this gap.
→The Onboarding Cold Start ProblemToken Exhaustion
The state reached when a team's collective AI usage exceeds quota limits, interrupting work mid-task. Distinct from individual rate limiting: at the team level, token exhaustion is a visibility and distribution problem — some teammates hit limits while others let quota expire unused. No current AI tool exposes collective capacity in real time.
→Token Exhaustion Is a Team ProblemMultiplayer AI
The emerging category of AI tooling that enables teams, not just individuals, to benefit from shared AI sessions. Analogous to the transition from individual code editors to GitHub: the individual layer (Claude Code, Cursor, Copilot) is mature; the team coordination layer — shared context, redundancy detection, quota visibility — is being built now.
→Multiplayer AI: The Category That Doesn't Exist YetCorrupt Success (AI Output)
An AI-generated output that passes surface-level evaluation (correct structure, professional language, appropriate length) while failing to deliver the substance required for action. Research finds 27–78% of AI task completions are corrupt successes. Distinguished from failures because they require active evaluation to detect — they look done.
→AI-Generated Docs Are Productivity TheaterTeam AI Brain
A shared knowledge layer that persists AI session outputs across teammates, enabling context retrieval instead of context rebuilding. A team AI brain gives every teammate — including new hires — access to the accumulated findings, decisions, and reasoning from all prior AI sessions without manual documentation or knowledge-base maintenance.
Session Context
The accumulated knowledge, reasoning, and decisions produced within a single AI coding or research session. Session context is currently ephemeral: it exists only within the active session and is lost when the session ends. Without a team AI brain, this context must be manually documented or rebuilt by the next person who needs it.
Redundancy Detection
An automated check that flags when a teammate is about to start AI work that overlaps with work already done by someone else on the team. Effective redundancy detection operates before tokens are burned — at session start — not after work collides at code review.
Quota Visibility
Real-time awareness of collective AI token usage across an entire team, including remaining capacity, usage by member, and time until reset. Quota visibility enables teams to redirect expiring capacity to backlog tasks and prevents mid-task interruptions from unexpected rate limiting.
See these concepts in action
Evols eliminates the handoff tax, cold start, and token exhaustion for your entire team with one CLI install.
Get early access