Audiobook Studio 2.0 docsPlugin Context Contract
Plugins get what they need through a context object, never by importing Studio's internals.
In progress: the context contract is being finalized in 2.0.
At a glance
plugin/corestays portable (no app imports).- A context is passed into Studio-facing adapters.
- Persistence stays Studio-owned.
Why portability matters
The engine core must run without Studio. Keeping it free of app imports is what lets engines be extracted and run standalone. See Portable Core & Standalone Repos.
The context
Studio passes a context into the plugin's adapter layer for the services it's allowed to use. Studio still owns persistence and state.