Entity types

The full list of product objects — in the interface and over MCP.

The full set of objects you work with in Flownix — in the interface and over MCP.

Top-level container. A user belongs to organizations; projects live inside them.

A product with a KEY and a Markdown spec. The root of the node tree.

A unit of work of any kind (epic/feature/plan/task/doc). Carries content, status, progress, tags and links.

A human-readable id like KEY-KIND-N (e.g. AF-TASK-30). You can address a node by it instead of the UUID.

A label for filtering and routing work: backend, frontend, db, infra, decision…

An entry in the node feed from a user or an agent. The audit trail: [plan]/[progress]/[decision]/[review]/[done].

A directed “A depends on B” edge. Defines execution order between tasks.

A cross-link between nodes. Bidirectional: outgoing references and incoming backlinks.

A semantic bidirectional edge between nodes: blocks/blocked_by, depends_on, related_to, duplicates, parent_of/child_of. Rendered on the graph.

A doc-kind node — a Markdown page in the project’s “Documentation” section.

A code review of a branch with iterations (each run is a new iteration with a commit and body). Links to nodes and lives in the “Reviews” tab.

A single review run: number, commit hash and a Markdown verdict. A review accrues iterations as fixes land.

A grouping of tasks for shipping. The tree can be viewed grouped by release.

A Personal Access Token for MCP. Shown once on creation; used as a Bearer token.

A reusable instruction for an AI agent (SKILL.md) that teaches correct AI-Flow usage.