generated from coulomb/repo-seed
Add workplan execution queue
This commit is contained in:
@@ -4,7 +4,7 @@ type: workplan
|
||||
title: "Workplan Execution Queue and Activity-Core Handoff"
|
||||
domain: custodian
|
||||
repo: state-hub
|
||||
status: proposed
|
||||
status: finished
|
||||
owner: codex
|
||||
topic_slug: custodian
|
||||
planning_priority: medium
|
||||
@@ -38,7 +38,7 @@ automations, and agent dispatch.
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T01
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "b69e3c7d-46be-4e88-b039-7aa82d653b53"
|
||||
```
|
||||
@@ -49,11 +49,17 @@ sequential, and parallel intent.
|
||||
|
||||
Done when queue semantics are documented without overloading lifecycle status.
|
||||
|
||||
Result 2026-05-23: added execution semantics for `manual`, `queued`,
|
||||
`scheduled`, `launching`, `paused`, `completed`, and `cancelled` execution
|
||||
states; `manual`, `queued`, `scheduled`, and `immediate` launch modes; and
|
||||
`sequential`/`parallel` concurrency modes. The `/execution/semantics` endpoint
|
||||
exposes the vocabulary and boundary notes.
|
||||
|
||||
## T02 - Separate Lifecycle From Execution Intent
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T02
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "4f48b4d4-7232-4e36-b4a2-03aaef684ab4"
|
||||
```
|
||||
@@ -63,11 +69,16 @@ execution intent lives in separate planning/execution fields.
|
||||
|
||||
Done when `active` no longer has to imply "dispatch a coding agent right now."
|
||||
|
||||
Result 2026-05-23: added separate execution intent fields on workstreams:
|
||||
`execution_state`, `launch_mode`, `concurrency_mode`, `queue_rank`,
|
||||
`execution_group`, and `scheduled_for`. Lifecycle `status` remains unchanged
|
||||
when execution intent is updated.
|
||||
|
||||
## T03 - Add Prioritized Workplan Stack
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "9237b778-4c83-4ebe-942e-79bae29aaa45"
|
||||
```
|
||||
@@ -78,11 +89,15 @@ optional concurrency grouping.
|
||||
|
||||
Done when a human can choose what starts next from a clear ordered list.
|
||||
|
||||
Result 2026-05-23: added `/execution/workplan-stack`, a dependency-aware
|
||||
ordered queue view using execution state, planning priority, queue rank,
|
||||
planning order, lifecycle status, and workstream/task blockers.
|
||||
|
||||
## T04 - Add Launch Request Records
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T04
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "a8366495-fd66-436e-b423-e24c3ffadbc9"
|
||||
```
|
||||
@@ -94,11 +109,16 @@ preference, and whether immediate agent pickup is desired.
|
||||
Done when UI/API actions can request implementation without losing intent in a
|
||||
plain status patch.
|
||||
|
||||
Result 2026-05-23: added durable `workplan_launch_requests` records and
|
||||
`POST /execution/launch-requests`. Launch requests capture requested actor,
|
||||
mode, priority, repo, branch preference, immediate pickup, notes, and metadata
|
||||
while updating execution intent separately from lifecycle status.
|
||||
|
||||
## T05 - Define Activity-Core Boundary
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T05
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "2ebf5186-9a92-476a-ac62-3588cc51fb31"
|
||||
```
|
||||
@@ -110,11 +130,15 @@ own scheduling, wakeups, and agent dispatch when available.
|
||||
Done when the boundary is explicit enough that implementation can proceed in
|
||||
State Hub now without trapping orchestration there permanently.
|
||||
|
||||
Result 2026-05-23: the execution semantics service defines State Hub as the
|
||||
state, ranking, and durable handoff owner, while activity-core owns schedules,
|
||||
wakeups, agent dispatch, and request execution once available.
|
||||
|
||||
## T06 - Dashboard Controls
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T06
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "7d1c9ec7-8130-4f26-92ae-754c6f28ea48"
|
||||
```
|
||||
@@ -125,11 +149,15 @@ intent, and manual versus immediate pickup.
|
||||
Done when a user can move a workplan into the queue without accidentally
|
||||
starting work, or explicitly request immediate pickup when desired.
|
||||
|
||||
Result 2026-05-23: added the dashboard Workplan Queue page with queue rank,
|
||||
launch mode, sequential/parallel intent, execution group, save, and request
|
||||
controls. Workstreams link to the queue page.
|
||||
|
||||
## T07 - Handoff And Scheduling Tests
|
||||
|
||||
```task
|
||||
id: STATE-WP-0049-T07
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "f819907b-0409-411e-82d1-564c2d543f86"
|
||||
```
|
||||
@@ -139,6 +167,10 @@ eligibility, and the State Hub/activity-core boundary contract.
|
||||
|
||||
Done when execution intent can evolve without contaminating lifecycle state.
|
||||
|
||||
Result 2026-05-23: added API tests for semantics, execution-intent updates,
|
||||
dependency-aware queue ordering, and launch-request creation. The tests pin
|
||||
that lifecycle status remains separate from execution intent.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- Workplan lifecycle status is separate from execution intent.
|
||||
|
||||
Reference in New Issue
Block a user