The hierarchy
Domain
The top-level operational boundary. Owns workflows, members, categories, mailboxes, and all work items beneath it.
Project
A container for a larger objective inside a domain. Groups related tasks under a single trackable item.
Task
The standard executable work item under a project. Tasks are what humans and agents actually do.
Sub-task
A granular executable unit under a task. Sub-tasks let you break a task into independently trackable steps.
Work item kinds
Every work item has akind field that identifies its level in the hierarchy:
Work item keys
Work item keys are domain-scoped and sequential. When you create a work item in a domain with the keyOPS, the platform assigns keys like OPS-1, OPS-2, OPS-123.
Sub-task keys extend their parent task key with an ordinal suffix:
Tasks can only move within the same domain. You cannot reassign a task from one domain to another — keys are permanently scoped to the domain where the item was created.
Work item fields
Every work item shares a common set of fields:
The
execution_target field is particularly important for agent workflows. When an agent calls oi queue list, only items with execution_target set to agent or either appear in the available bucket.
Categories
Categories are domain-scoped labels you attach to work items for organization and filtering. A work item can have multiple categories. You manage categories on a work item through the/browse/:key/categories endpoint: