One Store for composable business capability.
Apps, Data Products, automations, services, and whole business processes. Each is one governed Use Case package. Inspect it, adopt it, and run it in your own sovereign workspace.
Governed adoption
Acquired like a package. Reviewed like a change.
Legra resolves dependencies, rights, and price, then cherry-picks the signed release onto a branch. Tests and review precede merge.
Follow the adoption pathApps and Data Products are Use Cases.
A stereotype activates a profile and an experience. One identity runs through publication, adoption, execution, pricing, and outcome.
Universal package
Use Cases
Outcomes, personas, Stories, policies, tests, implementations, and offers in one package.
Application stereotype
Apps
Use Cases with a dedicated frontend or application experience.
Data Product stereotype
Data Products
Supply-side Use Cases with a DPROD projection for datasets, ports, offers, and contracts.
Execution profiles
Automations and transforms
Reusable work with typed inputs, outputs, permissions, and tests.
Callable profiles
APIs and services
Capability exposed through typed Story contracts. Purpose and authority stay in the graph.
The Store is a view over a federated exchange.
Publishers release from sovereign workspaces. Catalogs index authorized descriptions and offers. Ownership stays with the publisher.
Understand federated publicationInside every package
Adoption is a reviewable graph change.
You choose a signed release, see its full delta, and promote it through your own branch governance. The publisher writes nothing into your workspace.
Discover
Search by outcome, persona, concept, publisher, price, or trust evidence.
Inspect and resolve
See the signed release, permissions, dependencies, tests, provenance, and token quote.
Cherry-pick
Bring the immutable package and its lineage onto a workspace branch.
Validate and preview
Run validation, package tests, and security checks. Inspect the branch delta.
Review and enable
Merge through workspace governance. Organization policy then activates the capability.
Anyone builds. Use creates the economic signal.
When a package performs work, the journal records the package, Story, offer, inputs, and outcome. That evidence pays the creator alongside data owners, operators, and the network.
Adoption is free. Execution is zero-priced or carries a usage or outcome price. Self-operated infrastructure runs every feature.