Capability Roadmap
This roadmap is framed around user outcomes rather than internal implementation labels.
Now
- Reliable signal capture for development observations
- Structured local storage with portable data formats
- Baseline retrieval for captured context
Next
- Stronger candidate review workflows for promotion decisions
- Better duplicate detection during review
- Improved operator visibility into promotion throughput and quality
Later
- Richer canonical memory retrieval and filtering
- Stronger policy integration for memory governance
- Cross-workspace sharing patterns with explicit controls
What success looks like
The roadmap is successful when teams can show measurable improvements in:
- Time to onboard engineers and agents
- Repeat incident frequency
- Decision turnaround for known problem classes
- Confidence in AI-assisted changes under governance
Positioning commitment
We will continue to lead with capability language in external docs: capture, review, preserve, reuse.
Internal names (Kindling, Ember, Edda) remain useful as architectural anchors, not as the primary value story.
Back to: Development Memory System Overview →