130 lines
4.4 KiB
Markdown
130 lines
4.4 KiB
Markdown
---
|
||
id: CUST-WP-0072
|
||
type: workplan
|
||
title: "Backfill workplan flavor and depends_on across the fleet"
|
||
domain: infotech
|
||
repo: the-custodian
|
||
status: finished
|
||
owner: grok
|
||
topic_slug: custodian
|
||
flavor: planning
|
||
depends_on:
|
||
- STATE-WP-0092
|
||
created: "2026-09-14"
|
||
updated: "2026-09-14"
|
||
related:
|
||
- STATE-WP-0092
|
||
- RAIL-FAB-WP-0030
|
||
- COORDINATION-WP-0005
|
||
- CUST-WP-0060
|
||
origin: residual-policy
|
||
origin_ref: the-custodian/history/20260914-open-workplan-chokepoints.md
|
||
state_hub_workstream_id: "ffd7f5b6-66fd-501f-a858-20fae00dd14e"
|
||
---
|
||
|
||
# Backfill workplan flavor and depends_on across the fleet
|
||
|
||
Workplan 2 of 3 after `STATE-WP-0092`. Do not classify the fleet until
|
||
the canon and hub default-exclusion exist; otherwise flavor is
|
||
undocumented YAML.
|
||
|
||
This plan updates **existing** workplans, conventions, and agent-facing
|
||
templates. It does not implement hub schema. It does not promote
|
||
residuals into implementation just to shrink a count.
|
||
|
||
## Wait for schema and policy
|
||
|
||
```task
|
||
id: CUST-WP-0072-T01
|
||
status: done
|
||
priority: high
|
||
depends_on: [STATE-WP-0092]
|
||
state_hub_task_id: "cfd17138-0ae2-573d-9709-0fc87af2baf1"
|
||
```
|
||
|
||
Start backfill only after `STATE-WP-0092` has flavor and `depends_on`
|
||
indexed and default views omitting residuals. Until then this task stays
|
||
`wait`. Record the hub revision / workplan statuses that satisfy the
|
||
gate.
|
||
|
||
2026-09-14: STATE-WP-0092 is `finished` (`2a2d8bcd`). File/API work is in
|
||
`state-hub` main. Live primary schema is still `b5e6f7a8c9d0`, so residual
|
||
exclusion is not yet visible on production views. Founder instructed this
|
||
backfill to proceed on files. Hub views follow after alembic `c6f7a8b9d0e1`
|
||
is deployed.
|
||
|
||
## Classify open workplans (and their open tasks)
|
||
|
||
```task
|
||
id: CUST-WP-0072-T02
|
||
status: done
|
||
priority: high
|
||
depends_on: [CUST-WP-0072-T01]
|
||
state_hub_task_id: "e87ee326-10a8-5dce-a59a-5b9dc3236ba9"
|
||
```
|
||
|
||
For every non-finished workplan in registered repos, set `flavor:` to
|
||
one of `planning`, `implementation`, `refactoring`, `extension`,
|
||
`residual`. Default: keep current functional/NFR work as
|
||
`implementation` or `planning`; mark spawned leftovers and
|
||
`origin: residual` children as `residual` unless founder demand or a
|
||
named risk already applies.
|
||
|
||
Do not auto-promote. If demand or risk is already documented, change
|
||
flavor **away from residual** and record the reason in the file. Fill
|
||
workplan-frontmatter `depends_on` where the prose already names a
|
||
blocker workplan; do not invent edges. Per-repo edits stay in the owning
|
||
repos (ADR-001). This workplan coordinates and tracks coverage.
|
||
|
||
Done when a coverage table (repo, workplan id, flavor, depends_on
|
||
filled or none) is committed under `the-custodian/docs/evidence/` and
|
||
default hub open views drop the residual cohort.
|
||
|
||
2026-09-14: 116 open workplans classified (81 implementation, 22 planning,
|
||
10 residual, 2 extension, 1 refactoring). Coverage:
|
||
`docs/evidence/2026-09-14-flavor-backfill/`. Residuals were not promoted.
|
||
Live summary exclusion waits on STATE-WP-0092 deploy.
|
||
|
||
## Update conventions and templates
|
||
|
||
```task
|
||
id: CUST-WP-0072-T03
|
||
status: done
|
||
priority: medium
|
||
depends_on: [CUST-WP-0072-T01]
|
||
state_hub_task_id: "00b28231-b4e1-5ab4-9474-d771d378b35b"
|
||
```
|
||
|
||
Update `AGENTS.md`, `.claude/rules/workplan-convention.md`, session
|
||
protocol, and any repo-seed workplan template so new files include
|
||
`flavor` and workplan-level `depends_on`. State the agent rule: do not
|
||
implement residuals unless promoted. Point at `STATE-WP-0092` for hub
|
||
behaviour and `COORDINATION-WP-0005` for the later cross-repo mode.
|
||
Do not duplicate coordination-engine instructions here.
|
||
|
||
Done when a newly scaffolded workplan in this repo validates and the
|
||
convention text matches canon.
|
||
|
||
## Intakes: provenance vs flavor
|
||
|
||
```task
|
||
id: CUST-WP-0072-T04
|
||
status: done
|
||
priority: medium
|
||
depends_on: [CUST-WP-0072-T02]
|
||
state_hub_task_id: "81c5a43b-4369-53f0-b666-a4f409162521"
|
||
```
|
||
|
||
Keep `origin: residual` on intakes as provenance. Where an open intake
|
||
has already been promoted to a workplan, set that workplan’s flavor
|
||
consistently. Do not close intakes from this plan. Do not create a
|
||
parallel residuals queue.
|
||
|
||
Done when the residual intake list and residual workplan list can be
|
||
joined by `origin_ref` without double-counting them as two implementation
|
||
backlogs.
|
||
|
||
2026-09-14: 42 `origin: residual` intakes. 38 point at finished parents
|
||
(intake is the live leftover). 4 point at non-workplan ids. Zero open
|
||
implementation workplans are also residual-intake targets.
|
||
`docs/evidence/2026-09-14-flavor-backfill/intake-join.json`.
|