The Use Case Exchange
One Store for composable business capability.
Find an App, Data Product, automation, transform, API, service, or complete business process. Underneath, each is the same universal, governed Use Case package—ready to inspect, compose, adopt, improve, and put to work in your own sovereign workspace.
Governed adoption
As easy to acquire as a package. As reviewable as a change to shared knowledge.
Legra resolves dependencies, rights, permissions, and price before cherry-picking a signed release onto a non-default branch. Tests, preview, and review happen before merge and activation.
Follow the adoption pathOne identity, many views
Apps and Data Products are Use Cases—not neighboring silos.
A stereotype activates the relevant profile and experience without creating a second identity. The same stable Use Case remains visible through publication, adoption, execution, provenance, pricing, and outcome measurement.
Universal package
Use Cases
Machine-readable outcomes, personas, Stories, workflows, policies, concepts, dependencies, tests, implementations, rights, and offers.
Application stereotype
Apps
Use Cases with a dedicated frontend or other bespoke application experience—not a separate capability model.
Data Product stereotype
Data Products
Data-supply Use Cases with a DPROD-conformant projection for datasets, ports, policy, offers, and contracts.
Execution profiles
Automations and transforms
Reusable work with typed inputs, outputs, rules, permissions, implementations, and tests.
Callable profiles
APIs and services
Business capability exposed through typed Story contracts while retaining its purpose and authority in the graph.
The Store is a view over a federated exchange.
Publishers release from sovereign workspaces. Catalogs index authorized public descriptions and offers; no central catalog becomes the owner or global source of truth.
Understand federated publicationInside every package
Governed cherry-pick
Adoption is a reviewable graph change—not an opaque installation.
The publisher cannot write into your workspace or silently update what you run. You choose a signed release, see the complete implications, and promote it through your own branch governance.
Discover
Search by outcome, persona, concept, industry, stereotype, publisher, price, compatibility, or trust evidence.
Inspect and resolve
See the signed release, permissions, rights, dependencies, implementations, tests, provenance, and bounded token quote.
Cherry-pick
Bring the immutable package and its lineage onto a non-default workspace branch.
Validate and preview
Run profile validation, package tests, security and compatibility checks, then inspect the complete branch delta.
Review and enable
Merge through workspace governance. Only then can Organization policy activate the adopted capability.
Value follows use
Anyone can build. Actual use creates the economic signal.
Publishing an App or Use Case does not make it valuable by itself. When a package performs real work, its task tree and journal retain the package, Story, implementation, publisher offer, inputs, and measured outcome. That evidence lets the declared capability price reach its creator alongside payments for data, rights, resources, and network services.
Adoption can be free. Execution can be explicitly zero-priced or carry a modest usage or outcome price. Features remain available on self-operated infrastructure without subscription gates.