fig. 2.11.2: the five committed task states and the one that lives in a ref: active, a queued file whose claim ref exists fig. 2.11.2 · the five committed task states and the one that lives in a ref: active, a queued file whose claim ref exists.⛶ ACTIVE IS NEVER COMMITTED: IT IS A QUEUED FILE PLUS A CLAIM REF ONE BOX, ONE COMMITTED STATE (A FOLDER); ACCENT RING: THE STATE IN A REF CREATE OR BLOCKED WHILE A CHOICE IS UNRESOLVED QUEUED BLOCKED GRADUATE UNBLOCK ACTIVE: A QUEUED FILE WHOSE CLAIM REF EXISTS DERIVED AT STATUS TIME, NEVER COMMITTED DONE COMPLETE: THE PR MOVES IT FAILED FAIL AT A STOP CONDITION; REGENERATE UNDER A NEW ID CANCELLED CANCEL: OBSOLETE OR DUPLICATE TERMINAL · PRUNED AFTER 30 DAYS (SUGGESTED); PRS AND GIT KEEP THE HISTORY source: gated-swarm-starter docs/TASK-BOARD-DESIGN.md lines 21, 35, 45-54, 79 and scripts/task-claim.ts line 32 (f4a81c1) · taskLifecycle.data.ts
View in context: Claiming tasks with git refs → · All figures
Andrew Fribush , software and computer engineer in Austin. I build consequential systems where software meets institutions: finance, healthcare, commerce, government data, and the mechanisms that govern AI agents. Taking new engagements: hello@andrewfribush.com .