KYXO terminology (glossary)
Definitions of the core terms you will encounter across KYXO.
Estimated time: 5 min · Difficulty: beginner
Overview
Give users a single reference for KYXO vocabulary.
Anyone unsure what a KYXO term means.
| Term | Definition |
|---|---|
| Organization | Your company's top-level tenant. Contains all workspaces, users and settings. |
| Workspace | A group of related teams and work within an organization. |
| Space | A grouping of projects within a workspace. |
| Project | Where planning, requirements, testing and defects live. Modules are enabled per project. |
| Module | A capability you enable on a project — Planner, Requirements, Testing, Defects, and more. |
| Planner item | A unit of planned work (task, story, etc.) in the Planner module. |
| Requirement | A statement of what the product must do, with acceptance criteria. |
| Acceptance criteria | Conditions a requirement must satisfy to be considered done. |
| Test plan | A structured grouping of test coverage. |
| Test suite | A collection of related test cases. |
| Test case | A single verifiable test with steps and expected results. |
| Test run / execution | An instance of executing tests and recording results. |
| Defect | A reported problem, often linked to a failing test and the requirement it affects. |
| RBAC | Role-Based Access Control — permissions granted via roles. |
| Entitlement | Whether a module or capability is enabled for your organization. |
| Platform staff | KYXO operators (platform administrators / support agents) who run the platform itself. |
| Ask KYXO | The documentation-grounded assistant in the Help Center. |
| Autonomous delivery | The agentic SDLC command centre where AI agents help deliver work. |
| Display ID | A human-readable identifier such as REQ-10001 or TC-10001. |