Daily triage stuff

workplans/CUST-WP-0044-daily-statehub-wsjf-triage.md

@@ -4,13 +4,13 @@ type: workplan
 title: "Daily State Hub WSJF Triage"
 domain: custodian
 repo: the-custodian
-status: active
+status: finished
 owner: custodian
 topic_slug: custodian
 planning_priority: high
 planning_order: 44
 created: "2026-05-17"
-updated: "2026-05-17"
+updated: "2026-06-04"
 state_hub_workstream_id: "99993845-be6a-401d-be98-f8107014abed"
 ---
 
@@ -249,7 +249,7 @@ governance boundaries.
 
 ```task
 id: CUST-WP-0044-T06
-status: todo
+status: done
 priority: medium
 depends_on: [CUST-WP-0044-T02, CUST-WP-0044-T03, CUST-WP-0044-T04, CUST-WP-0044-T05]
 state_hub_task_id: "46c48fde-bb5f-4fe5-98cc-9cf788c98fc5"
@@ -269,6 +269,23 @@ Calibrate:
 Done when the daily review is useful enough to continue as a standing
 Custodian habit.
 
+**2026-06-04:** T06 complete after reviewing three consecutive activity-core
+daily triage notes:
+
+- `memory/working/daily-triage-2026-06-02-f9b97749.md`
+- `memory/working/daily-triage-2026-06-03-6d2737e3.md`
+- `memory/working/daily-triage-2026-06-04-65e273bf.md`
+
+The recommendations were stable and useful: `CUST-WP-0044` and `CUST-WP-0045`
+were repeatedly ranked as high-confidence `work-next`, human-gated work stayed
+clearly marked, and `CUST-WP-0046` remained visible as a revisit/unblock item.
+Calibration notes live in
+`docs/daily-statehub-wsjf-calibration-2026-06-04.md`. The main adjustment is
+that future executable JSON reports must include rank plus WSJF component
+scores; the schema, prompt, and ActivityDefinition were updated accordingly.
+The daily review is useful enough to continue as a standing Custodian habit,
+so `CUST-WP-0044` is finished.
+
 ## Acceptance Criteria
 
 - The Custodian has a daily review path for the State Hub situation.
@@ -282,7 +299,7 @@ Custodian habit.
 
 ## Implementation Notes - 2026-05-17
 
-The daily triage loop now has two explicit layers:
+The daily triage loop initially had two explicit layers:
 
 - Active runner: Codex app automation `daily-state-hub-wsjf-triage`.
 - Durable target substrate: activity-core ActivityDefinition draft at
@@ -292,12 +309,13 @@ The reusable prompt, report template, WSJF procedure, loose-end detectors, and
 recommendation gates live in
 `runtime/prompts/daily_statehub_wsgi_triage.md`.
 
-The activity-core definition is intentionally disabled while the Codex
-automation is the active runner. It exists so the schedule and context contract
-are reviewable in the same Markdown-as-definition style activity-core already
-uses. When activity-core can run a Custodian agent/report action directly, this
-definition should be enabled and the Codex app automation disabled, keeping a
-single daily runner.
+As of 2026-05-17, the activity-core definition was intentionally disabled while
+the Codex automation was the active runner. It existed so the schedule and
+context contract were reviewable in the same Markdown-as-definition style
+activity-core already uses. The intended target was to enable that definition
+and disable the Codex app automation once activity-core could run the
+Custodian report action directly.
 
-T06 remains open because it requires three actual daily runs and calibration
-against follow-up work.
+This changed after the activity-core cutover in `CUST-WP-0045`; the
+ActivityDefinition is now the active runner and the three-run calibration is
+complete.