Extend the platform. Keep one set of rules.
Kumwe extensions contribute capability through typed, owned contracts and install through a signed pipeline. The Extension SDK is published while adoption across App continues.
A component joins the platform without becoming the platform.
Extensions can add routes, workspaces, navigation, templates, capabilities and domain contributions under explicit ownership. Disablement or trust loss removes executable contributions while preserving owned data by default.
Inspect, verify, activate.
Package admission covers archive safety, strict manifests, signatures, compatibility and contribution ownership before a release enters the immutable runtime generation.
Published foundations, honest adoption status.
The Extension SDK provides public development contracts. Conversion is published as a focused package, and Producer is in founding development for repeatable project and package workflows.
Extension SDK
Published SDK contracts; integration and adoption continue in App.
Conversion
Published reusable conversion capability.
Producer
Founding development for extension project production workflows.
Build against the published boundary.
Start with the Extension SDK, then verify App’s current integration before depending on a capability.