Build the foundation before the modules.
Kumwe is becoming an ERP-capable application platform without becoming an ERP. The roadmap delivers safe extension contracts and shared runtime capabilities before domain modules are built.
Qualify App v2 and complete the shared core.
The v2 alpha has passed Gate A and is preparing for Gate B. Current work preserves portable databases, recovery, extension trust and delivery-surface parity while qualification evidence grows.
Finish the authoring journey and SDK adoption.
Studio must complete contextual creation and editing inside App, while the published Extension SDK becomes the normal route for governed extension development. Producer remains in founding development.
Prove client boundaries before shipping clients.
The Dart SDK remains a proposal and the Flutter client remains planned. Documentation and behavioural contracts come first; implementation follows qualified server APIs.
Extract stable contracts into focused packages.
Engine and package repositories are planned around boundaries already being proven in App. Extraction follows stability rather than creating a second, competing architecture.
The roadmap stops at ERP-capable platform contracts; accounting, inventory, CRM, payroll and other ERP modules are separate future components.
Use repository status as the current truth.
Plans explain direction. A passing gate, published package or merged implementation is the evidence for delivered behaviour.