generated from coulomb/repo-seed
Complete workplan state model cleanup
This commit is contained in:
@@ -4,7 +4,7 @@ title: Dependencies — Reference
|
||||
|
||||
# Dependencies — Reference
|
||||
|
||||
The Dependencies page shows the directed dependency graph between active
|
||||
The Dependencies page shows the directed dependency graph between open
|
||||
workstreams — which workstreams are waiting on others to reach a satisfactory
|
||||
state before they can fully proceed.
|
||||
|
||||
@@ -13,7 +13,7 @@ state before they can fully proceed.
|
||||
## What is a dependency edge?
|
||||
|
||||
A dependency edge **A → B** means workstream A cannot fully proceed until
|
||||
workstream B is in a satisfactory state (typically `completed` or `archived`).
|
||||
workstream B is in a satisfactory state (typically `finished` or `archived`).
|
||||
|
||||
Edges are used to model real sequencing constraints: for example, a shared
|
||||
library must reach a stable release before downstream domains can build on it.
|
||||
@@ -36,7 +36,7 @@ Each row shows:
|
||||
| **→** | Direction arrow |
|
||||
| **Blocked-by domain** | Domain of the prerequisite workstream |
|
||||
| **Blocked-by workstream** | Title of the workstream that must complete first |
|
||||
| **Status** | Current status of the prerequisite (green = active, grey = completed) |
|
||||
| **Status** | Current status of the prerequisite (green = active, grey = finished/archived) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user