Inspect dependencies and terms, then adopt a released capability under your own governance.
A reusable package brings a Use Case together with its relevant definitions, implementations, tests, and dependencies. Apps and Data Products use this shared package model.
Inspect the publisher, release, required data and services, access requirements, and terms. The package itself is free; using its dependencies can incur charges.
Bring a selected release onto a branch in the destination workspace. Review its changes and requirements, run the applicable checks, and decide whether to merge. Publication gives the upstream publisher no authority to change your workspace.
An update is another reviewed adoption decision. Forking preserves the relationship to the release from which your work began.
Executable Use Cases describes the common model. Composable Business provides an authoring interface. Find specific packages through federated discovery and the Registry.
Developer reference
A package release binds publisher identity, Use Case definitions, implementations, tests and dependency references. App/Data Product profiles specialize that shared identity model. RDF metadata makes the dependency and authority requirements queryable.
Resolution includes data/service availability, access grants, rights and prices. Type-compatible dependencies can still be inadmissible or unfunded.
Apply a selected immutable release to a destination branch; destination validation and review authorize merge. Upgrades select another release and undergo the same checks. Preserve publisher and fork lineage. Registry discovery metadata describes an available capability; it is not an installation receipt or authority to push updates into consumer workspaces.