Public Roadmap
Now, next, later, and research.
The roadmap is public but controlled. It avoids fixed dates unless release data provides them, and it keeps native runtime work clearly marked as future research unless the status changes.
Roadmap Groups
Each item renders from data/roadmap.json so the public site can evolve as work moves between phases.
Now
Public platform identity and the first official website surface.
Homepage, platform positioning, launcher portal, Ashfall page, modules catalog, docs home, and roadmap.
Player-facing world, systems, module, and install messaging for the first official experience.
Player, developer, platform, and troubleshooting docs stubs ready for MDX expansion.
Next
Make the platform more operational and release-aware.
Document manifests, channels, lockfiles, snapshots, integrity checks, and release gates.
Clear install, repair, profile handoff, Linux, and dependency troubleshooting paths.
Expand status, dependencies, docs links, GitHub paths, release notes, and Ashfall usage metadata.
Later
Grow the site into a real developer and release portal.
Separate docs by launcher, PackOS, module, and runtime contract versions.
Scaffold module templates, starter manifests, example providers, and integration samples.
A future interface for assembling ECHO-aware experiences from validated modules.
Research
Long-term native runtime direction without promising finished runtime support.
Explore native loader, renderer, world runtime, entity runtime, networking, and save format foundations.
Investigate save contracts that can outlive a single adapter target.
Marketplace-style discovery for official and community modules after validation systems mature.