Governed supply
A Data Product is more than data.
- Data and content
- Semantic models
- Interfaces and ports
- Provenance and quality
- Ownership and policies
- Dependencies and service levels
- Offers and commercial terms
Supply meets demand
Data Products are supply. Use Cases are demand.
Legra is the data logistics infrastructure that connects them. It turns demand from a project document into a machine-readable, executable package—and turns supply from a dataset into a governed product that can be safely put to work.
The package-manager benchmark for business capability
A governed product should become as easy to find, acquire, and integrate into a business process as a software package is to add to a project. But its meaning, ownership, authority, contractual terms, provenance, and economic value must travel with it.
Complementary packages
Machine-readable demand
A Use Case is more than documentation.
- Desired outcomes
- Personas and responsibilities
- Required concepts and data
- Stories and workflows
- Policies and authority
- Tests and acceptance criteria
- Composable sub-use-cases
Precise agreements
Three contracts cooperate. They are not interchangeable.
Product interface contract
Describes a Data Product port: what can be consumed, in which shape, and through which technical interface.
Bilateral Data Contract
Binds provider and consumer to rights, duties, service levels, delivery conditions, and prices.
Formation surface planned
Story invocation contract
Defines the typed inputs, outputs, persona, and behavior of one stable unit of business work.
From catalog to outcome
The product does not stop at publication.
01
Publish supply
A provider describes a maintained Data Product, its ports, dependencies, quality, policies, and offer.
02
Express demand
A consumer models the outcome, people, concepts, data requirements, behavior, policies, and tests as a reusable Use Case.
03
Discover and match
Federated catalogs can match semantic demand to suitable products, transformations, and services—not merely keywords.
Planned surface
04
Agree and authorize
The parties establish the applicable interfaces, rights, duties, delivery terms, authority, and complete price.
Planned surface
05
Integrate and execute
Legra resolves dependencies, brings authorized knowledge into context, and invokes the relevant Stories or Workspace App capability.
06
Prove the outcome
Journal evidence connects execution and results to actors, inputs, authority, changes, costs, and value flows.
Knowledge in data and code
Model what should be inspectable. Govern what remains code.
Concepts, facts, rules, shapes, policies, Stories, workflows, and tests become linked graph knowledge where modelling adds value. Specialized or existing code remains a first-class participant through typed Story boundaries.
One business contract, replaceable implementations
Graph statementsQueriesWorkflowsPipelinesAgent jobsUI actionsExternal APIs
The Story keeps meaning, inputs, outputs, authority, provenance, tests, and economic context in the living graph while the selected implementation can evolve.
Methods and standards
DPROD
The Data Product Ontology provides a standards-oriented foundation for describing Data Products and their contracts. Legra extends the operational route around them.
Visit the DPROD workgroupEKG Method
The Use Case Tree Method makes business demand composable and connects outcomes to the knowledge and behavior required to deliver them.
Explore the method