roadmap.mdx currently maintains its own independent description of project phases, instead of mirroring the established source-of-truth chain:
ADM Work Packages (opportunities-and-solutions.mdx) define scope — what needs to be built
Gitea Milestones + Issues define status — what's actually done, computed mechanically from real issue state
roadmap.mdx should only reflect milestone status and link back to the relevant WP for scope — it should not independently describe or duplicate content from either source
Action items
Restructure roadmap.mdx so each phase shows milestone status (linked to the corresponding Gitea milestone) and links to its corresponding Work Package in opportunities-and-solutions.mdx for scope detail, instead of describing scope/status inline
## Problem
`roadmap.mdx` currently maintains its own independent description of project phases, instead of mirroring the established source-of-truth chain:
- **ADM Work Packages** (`opportunities-and-solutions.mdx`) define scope — what needs to be built
- **Gitea Milestones + Issues** define status — what's actually done, computed mechanically from real issue state
- **`roadmap.mdx`** should only reflect milestone status and link back to the relevant WP for scope — it should not independently describe or duplicate content from either source
## Action items
- [x] Restructure `roadmap.mdx` so each phase shows milestone status (linked to the corresponding Gitea milestone) and links to its corresponding Work Package in `opportunities-and-solutions.mdx` for scope detail, instead of describing scope/status inline
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
roadmap.mdxcurrently maintains its own independent description of project phases, instead of mirroring the established source-of-truth chain:opportunities-and-solutions.mdx) define scope — what needs to be builtroadmap.mdxshould only reflect milestone status and link back to the relevant WP for scope — it should not independently describe or duplicate content from either sourceAction items
roadmap.mdxso each phase shows milestone status (linked to the corresponding Gitea milestone) and links to its corresponding Work Package inopportunities-and-solutions.mdxfor scope detail, instead of describing scope/status inline