How to read this page
This is the short public roadmap, not the full internal planning surface. Use it to understand:- the current direction of the product
- the active tracks that matter now
- what the project is explicitly not trying to become
Current direction
SpecPunk should move forward as a:- bounded correctness substrate
- durable stewardship layer
- simple operator shell
Active tracks
1. Execution reliability and rollback
Make bounded execution fail safely and predictably.2. Contract quality and structured targeting
Reduce free-text drift and improve source-first targeting.3. Repo fixture matrix and dogfood regression coverage
Turn repeated dogfood failures into named fixture coverage.4. Proof, gate, and typed evidence strengthening
Make decisions and proof artifacts easier to inspect.5. One-face operator shell
Keepgo, start, gate, and status as the obvious happy path.
6. Provider wrapping, not provider duplication
Adopt provider-native runtimes, tools, tracing, and session primitives through thin adapters.7. Bounded autonomous loop
Improve goal-to-result flow without turning autonomy into a giant subsystem.Not active roadmap items
These are not active default tracks today:- daemon-first rebuild
- custom universal agent runtime
- large internal memory platform
- always-on multi-model divergence
- provider-zoo UX
- research or council growth without a clear reliability payoff
Scope note
Examples are not part of the first public docs pass yet. The first goal is a clear explanation of the project, the current CLI path, and the active roadmap.Canonical source
The canonical current roadmap for the repository lives indocs/product/CURRENT-ROADMAP.md. This page is the short public version.