Spanda

Roadmap migration notes

Date: 2026-06-28

Summary

The Spanda roadmap was restructured into a product ecosystem presentation. Scope is unchanged — every feature, blueprint, and milestone from the prior docs/roadmap.md is preserved in ROADMAP.md.

What changed

Before After
Single docs/roadmap.md mixing language, ops, enterprise, blueprints ROADMAP.md at repo root with 8 Platform Pillars
Solution blueprints as a subsection Dedicated Official Solution Blueprints with 14 industries
Implicit product naming Explicit product family (Spanda Language, Runtime, Verify, Readiness, …)
Flat feature lists Feature ownership model (Core / Package / Provider / Blueprint / …)
Release tables only Timeline by maturity (Now / Next / Later / Long Term / Research)
Scattered diagrams Dependency maps (pillars → packages → providers → blueprints)

What did not change

Old anchor / habit New location
docs/roadmap.md#language ROADMAP.md § Pillar 1
docs/roadmap.md#runtime ROADMAP.md § Pillar 2
docs/roadmap.md#verification ROADMAP.md § Pillar 3
docs/roadmap.md#fleet ROADMAP.md § Pillar 4
docs/roadmap.md#packages ROADMAP.md § Pillar 8
docs/roadmap.md#tooling ROADMAP.md § Pillar 7
docs/roadmap.md#enterprise-operations ROADMAP.md § Pillar 6
docs/roadmap.md#official-solution-blueprints ROADMAP.md § Blueprints

For contributors

  1. Edit ROADMAP.md when adding or reclassifying roadmap items
  2. Update docs/feature-status.md when tier changes (Stable / Experimental / Future)
  3. Add industry-specific detail under docs/solutions/{industry}.md for new blueprints
  4. Keep docs/roadmap.md as a redirect — do not restore the monolithic document

For website / README