Checklists and dependencies

Member adds task checklist items, marks mandatory steps and links any same-board task dependencies. Distinguish the blocking task from the blocked task. Reject self-dependency and cycles before accepting the edge. Shared work needs an explicit task participants grant and active guest board membership; a mention or pasted file URL cannot add that permission.

Member requests a permitted move from the current column using the expected task revision. Resolve the active workflow revision, allowed source path, blockers and effective destination WIP limit. Reserve the destination and update current column plus derived Status atomically. Set started at on the first Doing entry of the current cycle, append task events and retain the order change. A drag, keyboard action or bulk request uses the same checks.

The move service consumes an Approved transition requests decision once, rechecking current revision, blockers, mandatory checklist policy and destination capacity. Mark Applied only when the move commits. Entering Done stamps completed at and appends one Completed task events row for Task plus cycle number. An approved request with no free slot remains approved but unapplied until it can be safely retried; approval alone is not completion.

Board Owner can reopen completed work through an allowed current workflow move with a recorded reason. Preserve the original completion event, increment cycle number and start a new work cycle without rewriting earlier timings. Recheck WIP and applicable approval policy for the destination. Archiving removes a task from active lists but preserves its relationships and event history; it cannot be used to remove evidence from an open review.

A launch task can depend on a reviewed document and a completed data import. Completing the document resolves that directed dependency only. The import remains a blocker until its own condition is satisfied. If the completed prerequisite is reopened, its dependency becomes active again. Earlier completed handoffs retain their history and show the changed prerequisite; they are not silently rewritten. Reversing the direction changes the meaning, so the board rejects a self-reference or cycle before accepting the link.

A checklist records work inside a task; a dependency links separately owned tasks. Required checklist items must be completed before Done. If policy permits a waiver, the owner records who granted it and why. A waived item stays distinguishable from completed work.

The transition rechecks current blockers and checklist state when it commits. An earlier preview does not reserve permission to finish. A new required step or unresolved dependency can prevent a reviewed handoff from applying. Keep the reason with the task so the contributor can resolve the missing work instead of repeatedly dragging the card.

• Active Blockers. Open the current records for this module within your assigned role and permitted scope.