Public product roadmap
Track product outcomes and maturity without converting internal estimates, implementation checklists, or experiments into delivery promises.
Current outcome
The current priority is a trustworthy release-candidate loop: discover effective capabilities, operate or connect a store, publish listings, complete supported checkout and payment paths, manage orders, preserve evidence, recover data, and understand every cost and responsibility.
Near-term outcomes
- Harden standalone installation, backup, upgrade, recovery, and release provenance.
- Complete coherent buyer and seller journeys across small and large screens.
- Keep hosted, standalone, marketplace, and sovereign compositions on shared contracts rather than product forks.
- Make API, event, webhook, MCP, extension, and Agent behavior discoverable and fail closed.
- Improve store administration, storefront presentation, shipping, identity, accessibility, and internationalization based on validated user needs.
- Publish compatibility and conformance evidence for capabilities claimed across distributions.
Exploration areas
AI-assisted store setup, Agent-mediated workflows, reusable commerce surfaces, richer marketplace operations, additional payment integrations, and new extension runtimes remain subject to capability, security, economic, legal, and release review. Exploration is not a delivery commitment.
How execution is tracked
Repository issues, projects, feature designs, audits, and migration checklists own implementation work. This page owns only the public product-outcome view. Dates, staffing estimates, branch names, file-level tasks, and private operating plans are intentionally excluded.