AI Coding Agent Memory & Semantic Change Control

nool task

Track units of work through a real lifecycle in the same ledger as the code that closes them, so what shipped and what was planned never drift apart.

  • Lifecycle: Open, Claimed, InProgress, InReview, Done.
  • Agents pick up tracked work with acceptance criteria attached.
  • Tasks close in the same ledger as the code that closes them.
nool task board

Why it matters

A task tracked in Nool is causally linked to the knots that closed it. "Done" means a specific, inspectable change landed — not just that someone updated a status field.

The lifecycle

Every task moves through the same five states. Acceptance criteria are checked at InReview (QA), not guessed at the end.

  • Open: unassigned, visible in the inbox.
  • Claimed: picked up, not yet started.
  • InProgress: active implementation work.
  • InReview (QA): acceptance criteria are checked here.
  • Done: finished and solidified.
nool task pick --id <id>
nool task start --id <id>
nool task qa --id <id>
nool task finish --id <id> --solidify

Pick up tracked work

Find unassigned work or resume what you already own before starting something new.

nool task inbox
nool task mine

Acceptance criteria are advisory, not a blocker

Criteria never block execution. They exist so QA has something concrete to check against, and so a task's definition of done doesn't live only in someone's memory.

nool task criteria set --id <id>
nool task criteria review --id <id>