Responsibility
A registry is responsible for the extension information it publishes and the infrastructure used to distribute releases. ExtensionMesh does not require all registries to be operated by one organization.
What independence means
- The operator controls the registry infrastructure and availability.
- The operator decides which extensions are published.
- Authentication and access rules may be specific to that registry.
- A connector can consume more than one compatible registry source.
Current documentation scope
The project does not yet publish a stable universal registry specification. The first implementation is being used to identify which metadata, release and authentication behaviors are genuinely shared.
Implementation-led
If you operate or plan an independent registry, concrete requirements and edge cases are more useful now than speculative completeness.
Useful contribution topics
- Real publication and release workflows.
- Authentication and entitlement requirements.
- Version compatibility and dependency metadata.
- Failure behavior, availability and caching.