Glossary

Use the glossary when docs, roadmap work, API automation, and agent workflows need the same product vocabulary.

Terms

Term	Meaning
Workspace	A separate One Horizon environment with its own members, teams, integrations, taxonomy, and data.
Team	A group inside a workspace used for planning, standups, reports, and analytics.
Initiative	Planned work such as a feature, project, product bet, or roadmap commitment.
Ongoing work	Recurring or operational work without a clean end date.
Todo	Simple personal work that is planned, in progress, or blocked.
Completed task	Finished work shown in the Journal, recaps, standups, reports, and measurement.
Bug	A defect that needs triage and repair.
Issue	A synced work item from a source issue tracker such as Jira, Linear, GitHub, or GitLab.
Pull request	Code review work from a version control provider. GitLab merge requests appear in the same delivery views.
Backlog	Intake area for work that is not scheduled yet.
Triage	Review point where work is routed, assigned, clarified, or declined.
Recap	Daily view of completed, planned, and blocked work.
Standup	Team update flow built from recaps.
Taxonomy	Workspace terms for goals, companies, products, skills, coding tools, and agents.
Document	Structured context that can stay attached to an initiative, todo, or workflow.
MCP	Model Context Protocol connection point for AI assistants.
Agent	App capability that can receive queued work.
Worker	Runtime that claims and executes an agent session.
Session	One visible unit of queued agent work.
Claim	Server-side lease that authorizes one worker to execute one session.

Do not use todo as a synonym for finished work. Use todo for unfinished personal work. Use completed task for finished work, whether it started as personal work, initiative work, bug repair, captured tool activity, agent work, or manual Journal entry.

For practical workflow entry points, start from Initiatives & Bugs, Planning, or Start building.