mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
CHANGELOG entries for the summary route + bounded lists, panel flood fixes, delegate collision-surface params, breaker revisit budget, squash-merge guard relief, stale-ref diff fix, team-match enforcement, manifest workspace fix, QA no-pre-claim. RAG corpus teaches agents the new delegate requirements, wrong-team remediate, and QA self-claim flow; dated delta appended to docs/map/_front.md.
3.4 KiB
3.4 KiB
Task States Reference
State Categories
Active States (Work happening)
claimed- Agent has ownership, about to startin_progress- Active workverifying- Self-verificationneeds_revision- Fixing QA issues
Waiting States (On hold)
blocked- Waiting on dependencypaused- Temporarily stoppedawaiting_qa- Ready for QA reviewawaiting_documentation- Ready for docsawaiting_pr_review- Assembled cell→root / root→master PR awaiting the in-path review gateawaiting_pm_review- Ready for PM approvalawaiting_ceo_approval- Major task, CEO review
Terminal States (Done)
completed- Work finishedcancelled- Work cancelled
Setup State
backlog- PM setup phase, not ready for work
State Transitions
Developer Flow
pending → claimed → in_progress → verifying → awaiting_qa
↑ ↓ ↑ ↓
└─ unclaim └── needs_revision ←──────┘
QA Flow
awaiting_qa → claim_review (claims; status stays awaiting_qa) → pass/fail
↓
pass: awaiting_documentation
fail: needs_revision
Documenter Flow
awaiting_documentation → claimed (claim_doc_task) → awaiting_pm_review
PR Review Gate (assembled PRs)
in_progress → awaiting_pr_review (cell PM submit_up / Main PM submit_root opens the PR)
↓
pr_pass: awaiting_pm_review (PR reviewer)
pr_fail: needs_revision (PR reviewer)
The cell PM's submit_up opens the cell→root PR and the Main PM's submit_root opens the root→master PR; both enter awaiting_pr_review for the in-path reviewer. Leaf developer tasks and branchless coordination roots skip the gate.
PM Activation
backlog → pending (a PM activates the task during `triage`)
Role-Restricted Transitions
| Transition | Allowed Roles |
|---|---|
backlog → pending |
cell_pm, main_pm |
claimed → pending (unclaim) |
assignee or PM |
awaiting_qa → awaiting_documentation |
qa only |
awaiting_qa → needs_revision |
qa only |
awaiting_documentation → awaiting_pm_review |
documenter, developer (parallel) |
in_progress → awaiting_pr_review (submit_up / submit_root) |
cell_pm, main_pm |
awaiting_pr_review → awaiting_pm_review (pr_pass) |
pr_reviewer only |
awaiting_pr_review → needs_revision (pr_fail) |
pr_reviewer only |
awaiting_pm_review → completed |
cell_pm, main_pm |
awaiting_pm_review → awaiting_ceo_approval |
cell_pm, main_pm (parent tasks only) |
awaiting_ceo_approval → completed |
ceo only |
awaiting_ceo_approval → needs_revision |
ceo only |
awaiting_ceo_approval → cancelled |
ceo only |
any other non-terminal → cancelled |
cell_pm, main_pm, ceo |
CEO Approval Notes
- Only parent tasks (no
parent_task_id) can be escalated to CEO - Subtasks are completed by their Cell PM, not the CEO
- The CEO reviews the complete feature via the parent task
Checking State
You don't poll task state directly — every flow verb returns a standardized envelope whose status and next fields tell you the task's current state and what to call next. Trust the envelope rather than guessing. To pull the full task context (criteria, prior notes, handoff), call evidence(task_id).