# Roadmap From 1.0.0-beta To Stable

## Stable Criteria

Slovo reaches stable `1.0.0` only after:

- compatibility rules are documented and exercised across multiple beta releases
- formatter and diagnostics schemas are frozen for promoted features
- `lib/std` has clear API stability tiers
- package/workspace behavior has deterministic version and dependency policy
- conformance tests cover normal user projects, not only narrow fixtures
- benchmark publication remains repeatable without becoming a performance claim

## Recommended Sequence

The detailed post-beta feature plan lives in
`docs/POST_BETA_ROADMAP.md`. Keep this file as the short stable-readiness
summary and use the public roadmap document when choosing the next connected
implementation scope.

1. Harden monorepo release tooling, install flow, and common build/run loops
   (`1.0.0-beta.1`).
2. Define runtime resource and host-error policy before broad IO and
   networking (released in `1.0.0-beta.2` with read-only text file
   handles plus narrow filesystem status and mutation calls).
3. Stabilize `lib/std` module boundaries and document beta-vs-stable APIs.
4. Improve language usability around entry points, `match`, concrete aliases,
   and concrete numeric completeness.
5. Expand package/workspace discipline before remote registry work.
6. Add networking only after resource/error policy is coherent.
7. Add serialization/data-interchange helpers before richer network libraries
   (released in `1.0.0-beta.7` with compact JSON text construction and JSON
   string quoting).
8. Promote concrete type aliases before generics so long concrete vector,
   option/result, array, JSON, and resource-handle signatures can be named
   without changing runtime representation (released in `1.0.0-beta.8`).
9. Design generics and collection unification from real stdlib duplication
   pressure.
10. Add editor-facing diagnostics, watch mode, and generated documentation
   improvements.
11. Freeze migration/deprecation policy and cut stable only after beta feedback.