Iterel vocabulary

Work and history

• Project — one product and its shared cloud history.
• Thread — a saved conversation. A task's conversation stays inside that task; informational Chats have their own threads.
• Task — one implementation objective with status, owner, context, environment, and review state.
• Round — one follow-up prompt, engine run, and receipt cycle on a task.
• Mission — a related-task grouping shown on the board, able to carry a target date and a PRD. The database still uses epics; product copy does not.
• PRD — a mission's product requirements document: the intent that seeds task specs and Build runs.
• Spec — a task's product contract: user story, acceptance criteria, edge cases, and notes.
• Triage — the queue of incoming requests, from a link, Slack, or a Linear import, waiting to be promoted into tasks.
• Agenda — the now/next job fulfilled by Command center, task status groups, notifications, and the “since you left” digest; it is not a separate destination.

Surfaces and outputs

• Stage — the main work area.
• View — a way to inspect the project or a task, such as Changes or Project Map.
• Artifact — a durable document produced by a capability, tool, or agent.
• File — a durable non-document output such as an image, logo, SVG, or upload.
• Assets — the panel where saved artifacts and files live with provenance.
• Context — project knowledge used by people, capabilities, and engines.
• Snapshot — a captured app state or repository state with lineage.

Intelligence and distribution

• Agent — a named, reusable and versioned specialist invoked once by @handle, retained by an Agent Chat, or assigned to a Task. General is the absence of an agent.
• Finding — immutable review evidence with an exact code, Design, Map, Whiteboard, artifact, Task, or runtime anchor and a separately adjudicated status.
• Tool — an implementation operation available to an agent or contextual + menu; never a separate product destination. Figma Import and Generate image are tools, not agents.
• Extension — the packaging and distribution unit for integrations and MCP-based additions.

Product copy never calls an extension a “plugin” or a “module.” An engine is where an agent runs, not the specialist itself, and Iterel is not a model.