generated from coulomb/repo-seed
Add WSJF triage dashboard review page
This commit is contained in:
@@ -10,6 +10,11 @@ belongs to exactly one project domain. The Workstreams page gives you a
|
||||
filtered, visual overview of active work, derived blocked state, and the
|
||||
dependency graph between workstreams.
|
||||
|
||||
The [Daily WSJF Triage](/wsjf-triage) page is a companion review surface for
|
||||
activity-core's daily recommendations. It links recommendation candidates back
|
||||
to workstream detail pages when the candidate can be resolved through the
|
||||
workplan index.
|
||||
|
||||
---
|
||||
|
||||
## Workstation Distribution chart
|
||||
|
||||
57
dashboard/src/docs/wsjf-triage.md
Normal file
57
dashboard/src/docs/wsjf-triage.md
Normal file
@@ -0,0 +1,57 @@
|
||||
---
|
||||
title: WSJF Triage
|
||||
---
|
||||
|
||||
# WSJF Triage
|
||||
|
||||
The Daily WSJF Triage page reviews the append-only reports produced by the
|
||||
Custodian daily triage runner. The producer is tracked by `CUST-WP-0044`; the
|
||||
dashboard page is only a read surface for `daily_triage` progress events.
|
||||
|
||||
The page loads the latest reports from:
|
||||
|
||||
```text
|
||||
GET /progress/?event_type=daily_triage&limit=14
|
||||
```
|
||||
|
||||
Each event carries the report under `detail.report`, with a summary and a list
|
||||
of recommendations. Candidate values are resolved through
|
||||
`/workstreams/workplan-index` so file-backed workplans can link to their
|
||||
workstream detail pages.
|
||||
|
||||
## How to read recommendations
|
||||
|
||||
Recommendations are advisory, not authoritative. They help decide where to look
|
||||
first, but they do not change workplan status, task status, ownership, or
|
||||
priority. Acting on a recommendation still belongs to the operator, the
|
||||
workplan owner, or a follow-up implementation workplan.
|
||||
|
||||
Confidence labels mean:
|
||||
|
||||
| Confidence | Meaning |
|
||||
|---|---|
|
||||
| high | State Hub summary, workplan file, and recent progress agree |
|
||||
| medium | Summary data is supported by at least one corroborating source |
|
||||
| low | The signal is stale, incomplete, or mostly inferred |
|
||||
|
||||
## Action vocabulary
|
||||
|
||||
| Action | Meaning |
|
||||
|---|---|
|
||||
| `work-next` | Best next executable task |
|
||||
| `close-out` | Finish closure review and mark done when appropriate |
|
||||
| `revisit` | Re-read and refresh before execution |
|
||||
| `split` | Break an oversized workplan into smaller plans |
|
||||
| `park` | Move out of active focus |
|
||||
| `needs-human` | Human decision or approval needed |
|
||||
| `needs-cross-agent` | Another repo or agent is the right owner |
|
||||
| `needs-consistency-sync` | File, DB, or index state should be reconciled |
|
||||
|
||||
## Pattern view
|
||||
|
||||
The pattern table aggregates recommendations in the loaded 14-day window. It is
|
||||
useful for spotting recurring human gates, stale revisit signals, or workstreams
|
||||
that keep surfacing as the next best piece of work.
|
||||
|
||||
No write controls live on this page. It is intentionally a review page so the
|
||||
daily runner remains a focus surface, not an execution loop.
|
||||
Reference in New Issue
Block a user