Key Concepts

This page explains the core concepts you will encounter throughout Fluxlix. Understanding how these pieces fit together will help you get the most out of the platform.

Organizations

An organization is the top-level account in Fluxlix. It contains all your projects, team members, and settings. Organizations are typically named after a company or team. You can invite members to your organization and control their access across all projects within it.

Projects

A project lives inside an organization and represents a distinct product, service, or initiative. Each project has its own Kanban board, backlog, repositories, workflow templates, and configuration. Most day-to-day work in Fluxlix happens at the project level.

Repositories

Repositories are connected Git repositories (such as a GitHub repo) linked to a project. AI agents use repositories to read and write code — cloning branches, committing changes, and opening pull requests. A project can have multiple repositories connected to it.

Work Items

Work items are the tasks, bugs, and features your team tracks on the board and in the backlog. Every work item has a type, a status, a priority, and optionally a parent item. The supported types form a hierarchy:

• Epic — A large body of work, made up of features
• Feature — A product capability, made up of stories
• Story — A user-facing unit of functionality, made up of tasks
• Task — A concrete unit of work to be completed
• Bug — A defect to be investigated and fixed

This hierarchy lets you break down large goals into actionable pieces while keeping everything traceable back to a parent epic or feature.

Statuses

Statuses represent the stages a work item moves through on the Kanban board — for example, Backlog, In Progress, In Review, and Done. Each project defines its own set of statuses, so you can tailor the board to match exactly how your team works.

Workflows

Workflows are visual automation sequences built in the Fluxlix workflow editor. They define the steps an AI agent or automation should follow — such as analyzing a work item, writing code, running tests, and opening a pull request. Workflows can be triggered by work item events, schedules, incoming webhooks, or chat messages. Fluxlix provides over 175 node types to build from.

AI Agents

AI agents are automated workers that can be assigned work items just like a human team member. When an agent is assigned a task, it follows the attached workflow: planning a solution, making code changes, committing to a branch, and creating a pull request. Agents surface their progress on the board in real time and can pause to ask questions or wait for human review.

Conversations

Conversations are chat threads where you can interact with AI to plan work, explore ideas, or run workflows through natural language. A conversation can be scoped to a project or tied to specific work items, giving the AI context about your codebase and backlog. Conversations can also be used to kick off or guide ongoing agent runs.