aim-coordinator-guide

To generate an atomic batch operations plan for a task pool, you formulate a POST /tasks/batch plan from Manager outputs, baseline facts, and rejected feedback. The plan includes only create and delete operations and requires explicit approval before execution.

A batch-atomic task pool update is a write operation that applies create and delete actions together as a single unit. This prevents partial updates and maintains task integrity by requiring explicit user approval before execution.

To coordinate manager output and baseline facts to update tasks, you cross-reference README targets against the current Task Pool. This process drafts a batch plan to add missing tasks or retire obsolete ones based on rejected feedback.

Yes, the batch plan includes per-entry details with task_id, title, spec, dependencies, and planning metadata. This ensures every create or delete operation in the atomic batch is fully specified before approval.

Your task pool update requires explicit approval before execution to prevent partial updates and maintain task integrity. The batch-atomic design ensures that formulated create and delete operations are validated against baseline facts prior to applying writes.