KOMU is not trying to ship a plugin marketplace yet. The current work is about establishing sane extension seams that can grow without rewriting the product.
Place JSON catalogs under:
extensions/playbooks
These catalogs can join the built-in playbook catalog during bootstrap.
Place JSON policy packs under:
extensions/policies
These policy packs are loaded into the security policy layer alongside the built-in rules.
Provider adapters are Python classes registered through the provider registry. The registry now supports explicit adapter registration so alternative bootstraps can add organization-specific providers cleanly.
These seams make it realistic to support later:
- organization runbooks
- enterprise policy packs
- cloud-specific integrations
- desktop-specific bootstraps
- alternative provider bundles
What is not implemented yet:
- dynamic Python plugin loading
- trust sandboxing for third-party code
- plugin dependency management
- signed extension manifests
Those concerns should come later, after the extension surface stabilizes.