tegwick
d8a2bb5c6b
Align dashboard reference pages with intake-as-discovery and suggestions as legacy, frame work records as unit vs structure artefacts, and add the ready STATE-WP-0076 plan for DoC/DoR quality policies. Include generated work-record index and recent legacy-meter evidence captures.
2.4 KiB
| 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:
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
/workplans/index so file-backed workplans can link to their
workplan 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 workplans 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.
Suggestions vs intakes
The triage page and some summary digests historically linked a ranked
suggestion backlog. That entity is retired for writes; open gated needs
are intake work records. ranked_suggestions on the state summary still
reads the legacy suggestion table (typically empty after migration). Live
intake backlog: GET /intakes/ — see Intakes and
Suggestions (legacy).