Public API terminology
| Term | Meaning |
|---|---|
| process | A repeatable routine that generates table, dashboard, detail, workflow, and history views. |
| process template | The versioned structure copied into a new tracked item. Editing it does not change existing items. |
| tracked item | One independent instance of a process with its own template snapshot and optional customisation. |
| standalone task | Independent work that does not require a process template. |
| company | Lightweight context and future-order defaults, not a CRM record. |
| order | A tracked item in the supported Orders process with purchase-specific fields and dates. |
| stage | A workflow section containing checklist tasks. |
| checklist task | One actionable step inside a stage or standalone task. |
| Home | A bounded cross-process summary. |
| Next Up | A computed queue of the most relevant open actions. It is read-only; mutate canonical resources. |
| Attention | A computed queue of work needing intervention. |
| archive | A recoverable lifecycle state removed from active views. |
| permanent deletion | Irreversible removal after preview/confirmation where required. |
Public documentation does not use database table, Convex document, CRM pipeline, assignee, team, or enterprise-administration language for these concepts.