Roadmap
Current Status
Section titled “Current Status”CARI (Code-Aware Retrieval Index) is production-ready with 92 tests passing across 5 implementation phases. The Knowledge Graph pipeline is functional but considered optional/advanced.
Short-term
Section titled “Short-term”Index Quality
Section titled “Index Quality”- Improved scoring heuristics for ranked retrieval
- Better handling of monorepo structures
- Support for more annotation source types
Language Support
Section titled “Language Support”- Python AST extraction (tree-sitter)
- Go AST extraction (tree-sitter)
- Rust AST extraction (tree-sitter)
- Generic fallback for unsupported languages (regex-based symbol detection)
Developer Experience
Section titled “Developer Experience”iw index watch— continuous re-indexing on file changes- Richer
reportoutput with actionable suggestions - Better error messages and onboarding flow
Medium-term
Section titled “Medium-term”Richer Signals
Section titled “Richer Signals”- Import/dependency graph integration into connections
- Test coverage correlation (if test framework metadata available)
- PR review history as a co-change signal
- Comment/TODO tracking
Editor Integration
Section titled “Editor Integration”- VS Code extension with inline drift warnings
- Hover providers showing CARI context for symbols
- CodeLens for annotation density
CI Enhancements
Section titled “CI Enhancements”- Pre-built GitHub Action (
uses: intentweave/check-drift@v1) - Support for GitLab CI, CircleCI templates
- Baseline comparison (track drift trend over time)
Knowledge Graph
Section titled “Knowledge Graph”The KG pipeline (LLM extraction → Neo4j) is functional but under evaluation:
- Useful for architecture exploration and decision archaeology
- Cost (LLM API calls) and complexity (Neo4j) limit adoption
- Keeping it as an optional advanced path
- May evolve based on community feedback and use cases
Contributing
Section titled “Contributing”Have ideas? See Contributing or open a GitHub Discussion.