Record the 2026-09-14 open-workplan chokepoint assessment and CUST-WP-0072.

Store the campaign analysis under history/ and add the fleet backfill
workplan for flavor plus depends_on, sequenced after STATE-WP-0092.

workplans/CUST-WP-0072-fleet-flavor-and-depends-on-backfill.md

@@ -0,0 +1,109 @@
+---
+id: CUST-WP-0072
+type: workplan
+title: "Backfill workplan flavor and depends_on across the fleet"
+domain: infotech
+repo: the-custodian
+status: proposed
+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
+---
+
+# 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: wait
+priority: high
+depends_on: [STATE-WP-0092]
+```
+
+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.
+
+## Classify open workplans (and their open tasks)
+
+```task
+id: CUST-WP-0072-T02
+status: wait
+priority: high
+depends_on: [CUST-WP-0072-T01]
+```
+
+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.
+
+## Update conventions and templates
+
+```task
+id: CUST-WP-0072-T03
+status: wait
+priority: medium
+depends_on: [CUST-WP-0072-T01]
+```
+
+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: wait
+priority: medium
+depends_on: [CUST-WP-0072-T02]
+```
+
+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.