Tasks and Impact

Tasks and impact

Choose Chat for an answer and Agent or Delegate conversation to Swarm for supervised work. Current agent task review lives in Swarm, not a separate generic Tasks page.

Request a bounded change

Name the goal, Project-relative paths, constraints, acceptance evidence and budget. For example: change game/main.gd, preserve save compatibility, update docs/DESIGN.md and report the exact Godot test/version. Proposed code in Chat does not prove files changed.

In Swarm select the Project and expand New request. Review Change request, coordinator Role and Token budget.

Preview before submitting

Use Preview impact before Submit request. Paths such as docs/DESIGN.md or canon IDs help identify graph seeds. No usable paths/IDs can produce no seeds. An empty graph result does not prove no effects, and preview is not execution.

Supervise and accept

Inspect Agents, Approvals, Integrations and Resource locks. Read the task tree, events, checkpoints, questions and evidence. A task question needs information; a broker approval concerns a specific tool/effect. They are different decisions.

Preserve IDs and errors on failure. Cancel the specific task and inspect owned processes/integrations; cancellation cannot undo an already completed external operation.

Success is not integration. Review files, validation, conflicts and integration records before accepting. Scripted workflows exercise leases, questions, worktrees and integration, but do not certify general model-driven game production. Follow the workflow cookbook and evidence limits.