reference · maturity
Maturity dashboard
The corpus's honesty about itself. Surfaces gaps the corpus names but doesn't yet address, plus pages overdue for review. Read at the quarterly portfolio review alongside DORA and VRI.
Maturity is a self-declared field on every page — gap / seed / draft / stable / reviewed. The dashboard below is built from the corpus's own frontmatter at build time.
222
Total pages
11
Gaps
132
Seed
69
Draft
10
Stable
0
Reviewed
Gap pages — areas the corpus names but doesn't yet address
- Artifact Lifecycle
- Chain Evolution
- Competitive Analysis
- Cross-Team Coordination
- Hiring for Chain Fit
- Infrastructure as Code
- Market & Competitive Awareness
- Pair Programming / Mobbing
- Quantitative Research
- Team Capacity Planning
- User Testing / Usability
Stale pages — last reviewed over 6 months ago
Everything is fresh.
What each level means
| Level | Meaning |
|---|---|
| gap | The area exists in the chain but is unaddressed in any volume. Filling it is part of the corpus's job. |
| seed | Stub: name, owner, volume reference. No prose. |
| draft | First-pass prose. May contradict other pages. |
| stable | Reviewed prose. Voice and facts hold. |
| reviewed | Recently re-checked against current practice. |
What to do with the dashboard
- Gap pages are inputs to the next cycle's practice sequencing. They tell the team where to invest in chain authoring next.
- Stale pages (>6 months since last review) are overdue. Re-read them in light of the cycles since; either confirm and bump
last_reviewed, or revise. - The total count is a portfolio health signal in its own right. A growing corpus with fewer gaps quarter over quarter is a chain that is learning.