Find published capabilities across participating registries without centralizing their contents.
A registry publishes descriptions of admitted packages: Use Cases, Apps, and Data Products. Each description identifies what is offered, who publishes it, and what its use requires.
The registry owner decides what qualifies for inclusion. A private workspace does not become discoverable simply because it is connected to Legra.
Registries can include other registries under declared admission rules. A search can follow those relationships while each registry retains its own identity and governance. Inclusion does not transfer ownership of the packages.
Finding a description gives a visitor information for a decision. Access to the described data and execution of its services still require their own authority and terms.
Registry explains participation. Reusable capability packages covers what happens after selecting a release. Browse the curated Registry listings for individual offerings.
Developer reference
A registry is a governed workspace. Inclusion edges compose its discovery scope with other registries; traversal searches eligible package descriptions, release IDs, publisher identities, dependencies and offers.
RDF descriptions keep ownership separate from discoverability. A public Data Product description can refer to private data without publishing its content. Registry admission and package execution have separate authorization paths.
A hit identifies an offering and selected metadata. It neither grants source-workspace membership nor certifies live service availability. Invocation still resolves source grants, accepted terms, funding and deployment context. Federation extends the discovery graph while preserving each workspace's disclosure boundary.