Task and mission context files

Code names and context files

A task or mission’s code name identifies its work context; the title describes the work. Code names are unique across tasks and missions in a project and are never reused there. They do not select an agent or confer permission to run anything.

Stable human-readable handles

Iterel renders current task or mission state as generated Markdown with an immutable basename. Copy that filename from the task or mission and paste it into another task, Chat, capability, or MCP-connected agent to reference the exact work object without duplicating its content.

What a reference contains

A referenced document can include the objective or mission purpose, current spec, status, latest accepted outcome, relevant rounds, and bounded Context Pack evidence. It is captured in the receiving round as a reference source, so it can inform comparison and continuity but cannot override the current task instruction or silently change mission grouping or dependencies.

Local materialization

For a bound machine workspace, Iterel materializes these generated documents under .iterel/task-context/. The files are projections over canonical task and memory state—not a second editable database. Cloud reads resolve the same filename through the project-scoped handle table.