The current model
ExtensionMesh separates the source of an extension from the code that integrates that source into a particular system. The separation keeps registry ownership independent and makes connector responsibilities explicit.
An independent extension source
A registry makes extension metadata and releases available. It controls its infrastructure, catalogue and publication process.
A system-specific integration boundary
A connector translates registry information into the discovery, installation and update mechanisms required by a supported system.
A distributable software package
An extension is the package described by a registry and consumed by a supported system through a connector.
The environment that manages extensions
System behavior is not assumed to be universal. Each connector owns the integration details required by its environment.
Why the boundary matters
A common model is useful only when it reflects real requirements. ExtensionMesh therefore keeps system-specific behavior visible and delays generalization until more than one implementation demonstrates the same need.
Terminology is still evolving
These terms describe the current project direction. They are not yet a frozen protocol or compatibility guarantee. Changes should be discussed publicly and accompanied by concrete implementation evidence.