coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

feat(terminology): prose sweep tool and custodian workplan cleanup (CUST-WP-0055 T04)
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 6s
Details

Browse source 
Add sweep_workstream_prose.py for agent-guidance files, sweep active workplan
prose in-repo, tighten scan allowlist exclusions, and update ADR-001 closure
protocol to workplan-first terminology.
This commit is contained in:
codex 2026-07-08 16:35:37 +02:00
parent 3bdefb3c4a
commit 2e0deee2ef
42 changed files with 312 additions and 186 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -31,7 +31,7 @@ promoting work into execution without human or agent review.
As of 2026-05-17, the State Hub snapshot shows:
- 24 active workstreams and 2 blocked workstreams
- 24 active workplans and 2 blocked workplans
- 184 todo tasks, 5 in-progress tasks, and 5 blocked tasks
- 5 open decisions
- several large active workplans with low completion ratios
@ -49,7 +49,7 @@ In scope:
MCP tools when available.
- WSJF assessment for open workplans and representative next tasks.
- Detection of loose-end patterns: stale active plans, large unstarted plans,
blocked work, open decisions, dependency-cleared work, zero-task workstreams,
blocked work, open decisions, dependency-cleared work, zero-task workplans,
and inconsistent file-backed state.
- A daily recommendation artifact that separates:
- work to do next
@ -75,7 +75,7 @@ Each daily run should collect:
- State Hub summary via `get_state_summary()` or `GET /state/summary`
- hub inbox via `get_messages(to_agent="hub", unread_only=True)` or
`GET /messages/?to_agent=hub&unread_only=true`
- open workstreams, open tasks, blocked tasks, blocking decisions, next-step
- open workplans, open tasks, blocked tasks, blocking decisions, next-step
hints, workplan index, and repo goal guidance
- relevant git status and consistency state for repos whose workplans are
likely to be touched
@ -98,7 +98,7 @@ Use a 1-5 scale for each numerator factor and denominator factor.
| Strategic value | Alignment with current Custodian, State Hub, Railiance, or dependency-chain goals. |
| Time criticality | Whether waiting increases operational risk, blocks other work, or lets context decay. |
| Risk reduction | How much the work reduces security, reliability, data-loss, coordination, or governance risk. |
| Opportunity enablement | How much the work unlocks other active workstreams or reduces future agent friction. |
| Opportunity enablement | How much the work unlocks other active workplans or reduces future agent friction. |
| Job size | Estimated effort and uncertainty; 1 is small/clear, 5 is large/uncertain. |
Formula:
@ -208,9 +208,9 @@ Signals include:
- active workplans with no recent progress
- large active workplans with many todo tasks and no in-progress task
- blocked workplans whose dependencies are now resolved or misclassified
- workstreams with zero parsed tasks
- workplans with zero parsed tasks
- high-priority workplans with stale `updated` metadata
- tasks still open after their parent workstream appears effectively complete
- tasks still open after their parent workplan appears effectively complete
- workplans whose file-backed state differs from State Hub state
Done when the daily report names concrete revisit candidates and the reason