Small contracts. One coherent platform.
Kumwe is preparing focused repositories for portable platform boundaries. Their public existence signals architecture and collaboration space; it does not mean those planned APIs have shipped.
Reusable behaviour below the application surface.
Planned packages cover deterministic representation, localisation, secret envelopes, sequences, idempotency, audit, approvals, transactions, automation, integrations, conversion adapters and bounded computation.
Typed records without turning core into an ERP.
Planned contracts separate contributions, access, definitions, relational schema, exact values, record models, queries, policies and reporting. Independently installable business modules can compose those capabilities later.
Keep every surface aligned.
Navigation, administrator, portal and business-surface contracts are planned to preserve capability filtering and application-service parity as the ecosystem grows.
Unless a card is explicitly marked Published, its repository is a planned boundary rather than a released package API.
The planned package directory.
These repositories expose intended ownership boundaries for collaboration. Their current status is planned unless a repository explicitly publishes a release.
Foundation contracts
Business runtime contracts
Delivery contracts
Use maturity labels as part of the API.
Choose published packages for present work and follow proposals or planned repositories when contributing to direction.