Roadmap¶
This roadmap describes publication gates, not delivery dates. An item moves forward only when its public artifact and validation evidence exist.
Available now¶
- bilingual Zensical hub with functional, data, technical, and Community tracks;
- initial public case and inventory-policy article with sources and limits;
- connected data catalog for Demand Planning, Supply Planning, and economic decisions;
- Community overview, architecture boundary, and first Demand → Supply workflow;
- official Community backend source, license, and v0.1.0 tag.
Version 0.1.0 is the official Community backend baseline. Later versions can add packaged distributions, reference data, and broader versioned contracts without changing the release status of this baseline.
v0.1.0 publication status¶
| Gate | Current status | Evidence required to advance |
|---|---|---|
| Public backend source | Published | The official repository and tag identify the exact v0.1.0 source |
| License | Published | LICENSE.md is present in the tagged source and referenced by the documentation |
| Backend build instructions | Published | The repository documents Java 21 and Maven prerequisites and commands |
| Local installation guide | In progress | A complete environment guide will extend the current build and datasource instructions |
| Packaged distribution | Planned for a later version | Compatible packaged artifacts will identify their source version |
| Reference dataset | Planned for a later version | Sanitized data will reproduce a documented Demand → Supply result |
| End-to-end workflow | Functionally documented | Automated or repeatable evidence proves Demand Plan and heuristic Supply Plan generation |
| Data and API contracts | Partially documented | Versioned schemas, endpoints, validation behavior, and examples match the tagged runtime |
| Project governance | Pending public artifact | Contribution, issue, security, compatibility, and release policies are public |
No gate is completed by intention or by a local build alone. The referenced public artifact and its validation evidence must exist together.
After v0.1.0¶
- expand product reference and troubleshooting by version;
- connect new articles and cases to durable concepts;
- publish compatibility and deprecation changes with each release;
- incorporate community feedback without turning the roadmap into a promise of dates.