Planned · Built · Governed · Visible · Validated
Platform Capability Roadmap
A feature is not complete merely because a file exists. This matrix verifies that every planned capability has a useful route, a governed registry record, a purpose-led entry point and a production-quality path.
1. Real capability
The page or function must solve a clear devotional, learning, discovery or operational need.
2. Governed route
The canonical route, publication state, source boundary and summary must be represented in the effective registry.
3. Correct visibility
The capability appears in the relevant purpose-led hub rather than being hidden or linked everywhere without context.
4. Production validation
Metadata, links, accessibility, responsive behaviour, PWA dependencies and deployment status are tested.
Deep plan reconciliation
Find plans that are connected, hidden, ungoverned or still missing.
Loading planned-versus-connected evidence…
Research discipline
Missing content and missing product capability are handled differently.
Missing devotional text requires source, edition, copyright and human-review evidence. A missing product route requires user need, information architecture, interaction design and performance/accessibility acceptance criteria. Neither is filled with generic generated content.
Devotional content queue Route recovery queue