Appearance
Glossary
Kendo-specific terminology for consistent communication across all agents.
| Term | Definition |
|---|---|
| Agent | An AI entity (Claude Code, custom bot, etc.) that can be assigned to issues and autonomously work on them |
| Agent assignee | An AI agent assigned to an issue, treated the same as a human assignee on the board |
| Board | Kanban-style view of issues organized by status columns |
| Backlog | List of issues not yet in active development — the "to be prioritized" queue |
| Epic | A grouping of related issues that together form a larger feature or initiative |
| Issue | The atomic unit of work in Kendo — a bug, feature, or task |
| Issue key | The unique identifier for an issue, formatted as PROJECT-0001 |
| MCP server | Kendo's Model Context Protocol server that lets AI assistants read and manage issues |
| Project | A container for issues, with its own board, backlog, and team members |
| Project code | Short uppercase prefix for a project (e.g., "KEN" for Kendo), used in issue keys |
| Tenant | An isolated instance of Kendo with its own database, subdomain, projects, and users |
| Worktree | Git worktree used by the Dev agent to work on issues in isolation without switching branches |
| Kendo HQ | This repo — the company-level orchestration layer containing agent profiles and shared context |
| Report | A lightweight feedback item (bug, request, idea) submitted to a project's triage inbox. Reports can be reviewed, reordered, promoted to issues (with optional AI story generation), or dismissed. Not an issue until promoted. Reports can be created in the UI or programmatically via the project API (source-tagged Api). |
| Lane | A configurable status column on the board (e.g., To Do, In Progress, In Review, Done). Each lane has a name, color, and order. Projects can customize their lanes. |
| Label | A project-scoped, colored tag applied to issues. Defined in project settings, applied from the issue sidebar or directly on board cards, and usable as a board/backlog filter. Changes broadcast live to all clients. |
| Priority | Issue urgency level — Highest, High, Medium, Low, or Lowest |
| Role | A custom permission set within a tenant. Each role defines per-action scopes (None, Own, All). Admin and Member are the default system roles; tenants can create additional roles. |
| Notification | An in-app alert triggered by issue changes, comments, assignments, or other events. Users can configure notification preferences and mark notifications as read. |
| Attachment | A file uploaded to an issue or comment |
| Sprint status | The lifecycle state of a sprint — planned, active, or completed. When completing a sprint, unfinished issues migrate to a target sprint or the backlog. |
| Blocking relation | A dependency between issues — an issue can block or be blocked by other issues. Displayed on the issue detail and managed via the board or MCP. |
| Issue template | A reusable template for issue creation within a project. Templates define default content that pre-populates new issues. Managed in project settings. (Renamed from "system prompts" internally.) |
| Two-factor authentication (2FA) | Optional TOTP-based second factor for user accounts. Each custom role carries an enforce_2fa boolean — tenants can require 2FA on any individual role (admins, billing approvers, etc.) without forcing it on everyone. Setup includes QR code and recovery codes. |
| BYOK AI keys | "Bring your own key" — tenants and projects can configure their own Anthropic or OpenAI API keys instead of using Kendo's shared keys. Managed at tenant and project level. |
| Hand to Claude | Hands a single issue to an autonomous Claude multi-agent (coordinator + planner + implementer + reviewer) that plans, implements, runs tests, and opens a PR. A pre-flight eligibility check grades the issue against a clarity/scope rubric and gates the hand-off. |
| Project API token | A project-scoped API token that lets an external application connect to a Kendo project programmatically — e.g., to pipe reports/feedback into the triage inbox. |
| Feature Planner (ALPHA) | Built but gated, not yet GA. A chat-based AI assistant that helps break a feature idea into well-scoped user stories through conversation, pulling context from existing issues and code before drafting. Not for external messaging until the tag is cleared. |
| OAuth | Third-party login via Google or GitHub. Users can link/unlink OAuth providers in their profile settings. Also used for invite acceptance. |
| Overview (issue view) | A dedicated issue overview page alongside Board and Backlog, showing issue summaries and key metrics for a project. |
| Epic status | The lifecycle state of an epic — Open, In Progress, or Completed. |
| kendo-red | #c8553a — the brand accent color used throughout the UI. See brand-guide.md for the full color system. |
Related
- ../company/product-overview.md — Features referenced in this glossary
- ../company/brand-guide.md — Visual identity and design tokens
- user-personas.md — Who uses these terms and in what context