Jeston plugin extensions must declare permissions before setup. This creates a reviewable boundary for extension behavior and prevents a plugin system from becoming an unbounded source of hidden coupling.
Why this matters
Jeston's design keeps the runtime explicit. The framework gives teams a place to express the contract, while the application remains responsible for provider choice, policy, failure handling, and operational measurement.
A practical reading rule
Separate supported behavior from experimental work, roadmap items, catalog metadata, and application responsibilities. That distinction is essential when adopting a framework and when writing upgrade documentation.
This article is part of a technical series about Jeston by Kvant. The source of truth is the official repository. Verify the current package and documentation before applying any example to production.
Top comments (0)