coulomb/state-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(terminology): workplan-first dashboard and retirement backlog (STATE-WP-0069)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Add the ranked legacy-interface backlog (T01), rename dashboard navigation and
user-facing copy to workplan while preserving wire-compat API keys (T02), and
activate the retirement workplan with T01/T02 marked done.
This commit is contained in:
tegwick 2026-07-08 16:08:32 +02:00
parent 4dc69bb8f5
commit b2264d1f06
44 changed files with 382 additions and 253 deletions
Download patch file Download diff file Expand all files Collapse all files

14
dashboard/src/docs/workstream-lifecycle.md
View file

@ -1,10 +1,10 @@
---
title: Workstream Lifecycle - Reference
title: Workplan Lifecycle - Reference
---
# Workstream Lifecycle - Reference
# Workplan Lifecycle - Reference
A workstream is an information object that occupies a named lifecycle state.
A workplan is an information object that occupies a named lifecycle state.
The stored `status` field keeps that state, while the task-flow engine derives
which other states are reachable and which exit assertions are blocking
movement. Dashboard health filters such as `needs_review` and `stalled` are
@ -43,7 +43,7 @@ backlog -> proposed -> ready -> active -> finished -> archived
| **stalled** | Task counts + timestamp | Work started, but there has been no meaningful progress after the threshold |
`needs_review` and `stalled` can appear beside lifecycle states. They should
not be written into workplan frontmatter or directly into the workstream
not be written into workplan frontmatter or directly into the workplan
`status` field.
---
@ -70,8 +70,8 @@ behind explicit tooling, not done silently.
## Flow Operations
```text
get_flow_state(entity_type="workstream", entity_id="<uuid>")
advance_workstation(entity_type="workstream", entity_id="<uuid>", target_workstation="finished")
get_flow_state(entity_type="workplan", entity_id="<uuid>")
advance_workstation(entity_type="workplan", entity_id="<uuid>", target_workstation="finished")
```
Direct status patching still exists for bootstrap and compatibility work:
@ -82,5 +82,5 @@ curl -X PATCH http://127.0.0.1:8000/workplans/<uuid>/ \
-d '{"status": "finished"}'
```
Workstreams are never hard-deleted. Use `finished` for completed
Workplans are never hard-deleted. Use `finished` for completed
implementation and `archived` for historical records outside normal planning.