Register use cases, apps, and data products; find them in one search; adopt them under review.
A registry is a workspace with admission rules: what a package must declare, the checks it must pass, and who reviews it. Its owner sets those rules.
A package represents a Use Case. Apps add dedicated interfaces; Data Products offer governed information. Particular offerings have their own entries in the Registry.
Independent registries can participate together while retaining their own rules and packages. Federated discovery explains inclusion and search across them.
Select a release, inspect its requirements, and review it in your destination workspace. Reusable capability packages owns the adoption, update, and dependency model.
The Executable Use Case model connects these packages to outcomes and authorized actions. Pricing explains the difference between a free package and the services it uses.
Developer reference
Registry admission checks package profile, publisher, immutable release identity, dependencies and terms. SHACL constrains declared RDF metadata; App, Data Product and other Use Case profiles specialize a common package model.
A valid catalogue entry can still require consumer-specific access agreements, paid dependencies or configuration before invocation. Admission is not execution certification.
Inclusion edges define reachable registry descriptions. Consumers resolve a pinned release into their branch workflow, then apply local validation and review. Catalogue operators govern admitted descriptions; they acquire neither mutation rights over consumer workspaces nor authority to install upstream updates silently. Publisher lineage and destination commit identity remain independently inspectable.