Marketplace and registry
Marketplace and registry views expose the releases you can use through Installable Products. Browse finds a Product. Its exact release supplies the content and requirements. Installed state shows what the Workspace actually holds.
Ownership
The Marketplace reads releases under the caller's access. Each release keeps its key, version, digest, publisher, and date. Owned content and referenced Products share that identity. Source attestation and payload digests keep proof of the bytes. They do not create a second release identity.
A Product wraps one root Block. A Block is a reusable capability bundle, and it can contain child Blocks. The exact release page shows the root Block and its child Blocks. A child Block is part of its Product. It has no key, version, or Marketplace listing of its own. Older releases have no Block tree. Their page lists the Products they build on instead.
Each release says who offers it. Merulan offers built-in releases. Your company offers the releases it publishes. Apps and Models stay in the Marketplace beside Products. Installed Products lists only what your Workspace installed.
The Console gives each Marketplace read a destination.
| Read | Console route |
|---|---|
| Browse releases | /marketplace/browse |
| Registry state | /marketplace/registry |
| Installed state | /marketplace/installed |
| Workspace composition | /marketplace/workspace |
| Exact release | /marketplace/products/[productKey]/[productVersion] |
| Install preview | /marketplace/preview/[productKey]/[productVersion] |
Lifecycle
The registry holds fixed releases. A tenant-authored release publishes as publisher_private. The published content must match its previewed digest and publishing company. Publishing the same bytes again returns the saved receipt. Different bytes at the same key and version are refused. A changed release needs a new version.
Marketplace discovery comes before install. Use the release preview contract to check the release against the target Workspace. Read that plan before you accept it.
Boundaries
Marketplace access comes from registry policy. A Product author cannot grant access through an authored field. Company releases stay within their publishing company. Entitled releases need a grant for the exact Product key. Anonymous discovery admits only Merulan-published releases whose distribution is public. Finding a release grants no right to install it.
A visible release does not grant anonymous installation. Check the caller's access before planning an install from it.
Failures
The registry reports a release you cannot discover as absent. That result does not reveal whether another caller can see it. Check the exact key, version, and active Workspace when a read finds no release. A digest mismatch means the submitted bytes differ from the accepted preview. Publishing those bytes fails.
Recovery
Marketplace recovery uses the read that matches the problem. If discovery fails, check the key, version, and access with the publisher. For installed state, use the installed inspection contract. Installed inspection retains provenance after discovery entitlement is lost. The read leaves saved installs and references unchanged.
For changed source bytes, preview the intended version again and keep its digest with the publication result.
Related
- Composition and workspace bundles explains how exact releases form a larger design.
- Installation profiles and bindings explains the choices a release asks you to resolve.
- The Console guide explains access to Marketplace views.