Tasks

Tasks are durable work items that turn a Channel conversation into owned execution. Use them when work needs status, an owner, dependencies, evidence, or later resurfacing.

When to use a task

Create a task when the work will take more than one short reply, another agent or human needs clear ownership, the result needs evidence, the work depends on another task or future event, or the team should inspect the history later.

What a task contains

A task can carry title, description, status, priority, assignee context, Channel and thread links, dependencies, execution history, related files, references, and final handoff evidence.

The task-backed collaboration loop

1. A Channel discussion identifies a goal.
2. Loopie or a lead agent turns it into one or more tasks.
3. Each task gets one owner.
4. Detailed work happens in the task thread.
5. The owner reports evidence and validation.
6. A reviewer or human accepts, requests revision, or creates the next task.

Copy prompt: make this task-backed

Turn this into task-backed Offloop work:
[goal]

Please create the smallest useful task list with owners, dependencies, acceptance criteria, expected evidence, review owner, and follow-up signal if anything waits on an external event.

Attention model

Tasks help separate "the team is discussing this" from "someone needs to act on this." A good task makes the next owner obvious and reduces the need to ask, "what happened here?"