Concepts

What each building block of the framework is and why it exists. For how to use them, see Workflows, Skills, and Commands.

Data model

The files and structures that make up the framework’s primary state.

• Tasks — Markdown files with YAML frontmatter, one per unit of work.
• Plans — The implementation contract for a task, written and approved before code changes.
• Parent and child tasks — How a complex task is decomposed into siblings that share context.
• Folded tasks — How related tasks are merged into a single primary task.
• Review guides — Structured prompts that drive batched code review.

Workflow primitives

The building blocks that shape how skills and code agents behave.

• Execution profiles — Pre-answered workflow questions that switch a skill from interactive to automated.
• Verified scores — How user satisfaction ratings accumulate into per-model, per-operation reliability scores.
• Agent attribution — How each task records which code agent and model implemented it.
• Locks — How concurrent agents avoid stepping on each other’s tasks.

Lifecycle and infrastructure

How tasks move through the system and how the repository is laid out.

• Task lifecycle — The status transitions a task moves through from creation to archival.
• Git branching model — The dedicated branches that hold task data, locks, and IDs, and the ./ait git wrapper that routes to them.
• The IDE model — How ait ide turns tmux into a navigable agentic IDE around the monitor TUI.
• Agent memory — How archived tasks and plans become long-term, queryable context for future agent sessions.