Project Roadmap
This file tracks future infrastructure improvements and project priorities. For content-specific tasks, see the Enhancement Queue.
Current State (January 2026)
Section titled “Current State (January 2026)”The project has mature infrastructure:
| System | Status | Notes |
|---|---|---|
| Validation Suite | ✅ Complete | 14 validators covering style, links, MDX, Mermaid, staleness, redundancy |
| Quality Grading | ✅ Complete | Claude API-powered grading (0-100 quality/importance) |
| Dashboard | ✅ Complete | /dashboard/ with quality distribution, /dashboard/graph/ for relationships |
| Knowledge Base | ✅ Complete | SQLite cache with article/source extraction and AI summaries |
| Resource Linking | ✅ Complete | <R> component with bidirectional tracking, metadata extraction |
| Page Type System | ✅ Complete | overview/content/stub classification |
| Freshness Tracking | ✅ Complete | reviewBy, contentDependencies, staleness validator |
Future Work
Section titled “Future Work”Content Quality
Section titled “Content Quality”-
Batch content improvement - Systematically upgrade high-importance, low-quality pages
- Use
node scripts/page-improver.mjs --listto identify priorities - Target: All pages with importance > 60 and quality < 40
- Use
-
Citation coverage - Many pages lack external citations
- Resource manager can convert links:
npm run resources process [page] --apply - Goal: Every substantive claim has a source
- Resource manager can convert links:
Tooling (Low Priority)
Section titled “Tooling (Low Priority)”-
Vale integration - Prose linting for terminology consistency
- Would catch mechanical style issues (hedging, passive voice)
- Deferred: Current validators cover structural issues well
-
VS Code snippets - Scaffolding templates for new pages
- Low effort (~30 min), zero installation
- Templates for: risk, response, model, debate pages
Style Guide
Section titled “Style Guide”-
Model page guidance - Models need different structure than risks/responses
- Mermaid diagrams, quantitative tables, scenario analysis
- Could be
model-1.0or expand kb-2.0 with “Model Pages” section
-
Component usage patterns - Document when to use:
- EstimateBox vs plain tables
- Mermaid diagrams vs prose explanations
- KeyQuestions component
Completed
Section titled “Completed”December 2025
Section titled “December 2025”Infrastructure:
- Quality dashboard at
/dashboard/ - Freshness tracking (
reviewBy,contentDependencies, staleness validator) - Page type system (overview/content/stub)
- Redundancy detection validator
- Wiki statistics on About page
- Mermaid diagram validator
- Comparison operator validator
- Dollar sign escaping validator
Content:
- Entity naming refactor for consistency
- Parameter pages restructured
- Concepts directory page (LessWrong-style layout)
Earlier
Section titled “Earlier”- kb-2.0 style guide
- Full validation suite (style, links, MDX, data integrity, etc.)
- Knowledge base system (scan + summarize)
- Resource manager CLI
- Quality grading system
- Don’t over-engineer - Add tooling only when manual process becomes painful
- Style guide is guidelines, not law - Adapt to content, don’t force templates
- Run
npm run validatebefore committing to catch issues early