Let’s make
it official.
Turn data, knowledge, rights, work, and agreements into a living graph.
Legra connects sovereign graph workspaces. People, organizations, and agents agree, work, and exchange value — with the evidence to prove it.
- Contents
- Governed Data Product
- For
- Executable Use Case
- Rights
- ODRL policy · 1 activity
- Budget
- 1,200 tokens authorized
- Custody
- encrypted blocks · 3 replicas
- Evidence
- journal #1284 · signed
Agent autonomy runs on governed context.
Agents fork production, do the work, and hand the branch on. It merges when everyone is satisfied and the rules pass — like everyone else's.
- 01
Discover and mount context
Agents mount relevant workspaces and Data Products.
- 02
Work on a fork
Complex work and what-if scenarios run on a fork of production, compared by diff.
- 03
Hand over
The branch passes to the next person or agent until everyone is satisfied and SHACL passes.
- 04
Merge with evidence
Approved work merges. The journal records who, under whose authority, with what result.
Start with the outcome you own.
Same infrastructure. Different reasons to care. Switch anytime.
View all perspectivesBusiness
C-level, lines of business, strategy, business architects
Turn data and organizational knowledge into strategic capability, stronger AI, governed Data Products, and participation in the global data economy.
FollowOrganization
Analysts, PMO, finance, HR, legal, compliance, governance
Reduce coordination, integration, and rework by making complex Use Cases, processes, authority, evidence, and organizational knowledge executable.
FollowData
Modellers, data architects, ontologists, data management
Build a semantic layer and Enterprise Knowledge Graph across messy legacy sources, then publish governed Data Products that real Use Cases can consume.
FollowTechnology
Engineers, designers, DevOps, solution architects
Use distributed graph infrastructure for RDF and LPG workloads, governed agent execution, encrypted workspaces, versioned change, provenance, and secure interoperability.
Follow
Data Products are supply. Use Cases are demand.
One capability model. Data Products supply, Use Cases demand, Apps add a dedicated front end. Each keeps its outcomes, people, concepts, data, stories, workflows, authority, and tests in the graph.
Legra runs the logistics between them: publication, discovery, semantic matching, agreement, delivery, execution, evidence, and value exchange. The Use Case Exchange presents Apps, Data Products, transforms, and services as views over the same package graph.
Governed supply
Data Product Use Cases
Governed supply: meaning, ownership, policy, and contracts in a DPROD-conformant projection.
Machine-readable demand
Use Cases
Composable business capability with executable stories, policies, and tests.
Dedicated experience
Apps are Use Cases
An App is a Use Case with a dedicated front end.
Model what is inspectable. Govern what remains code.
Concepts, rules, policies, stories, and tests live in the graph. Specialized code stays behind explicit execution boundaries.
Model-driven operation
Apps are Application-stereotyped Use Cases.
The graph owns purpose, concepts, stories, policies, and tests. The App binding supplies the front end.
Governed implementation
Stories make existing code part of the graph.
One business contract resolves to queries, workflows, agent jobs, or external APIs — with typed inputs, outputs, authority, and provenance.
Private pod to bounded transaction
Participate in the data economy. The source workspace never transfers.
- 01
Keep the source private
Owners keep sensitive knowledge in their sovereign workspace.
- 02
Describe the boundary
Name the Data Product, rights, duties, and price involved.
- 03
Authorize bounded use
Grant only the authority the agreed activity needs.
- 04
Execute and settle
Execute, return the result, settle value. The source workspace never leaves.
The operating layer of the data economy
Data logistics turns data activity into evidenced economic activity.
The network moves governed data, enforces rights, records what happened, and settles every valid claim. Owners participate economically. Providers run the infrastructure and get paid.
The token economy network
These are roles, not platform silos. The same individual or organization may occupy several roles in one activity.
Demand and budgets
Supply and demand meet
Governed, priced activity
A graph-defined Use Case composes data, rights, capability, resources, services, authority, and a token budget.
Tokens authorized before work
Zero remains an explicit price
Evidence substrate
Task tree + activity journal
Data, rights, services, and outcomes move toward useful work
Tokens, credits, refunds, rewards, and allocations move among parties
Evidence-backed settlement can reach
- owner
- creator
- operator
- provider
- NetworkOperator
The AI substrate for business work
Code has GitHub. Business AI has Legra.
Coding agents improve a shared, versioned corpus. Business agents get the same: data, documents, rules, decisions, and evidence organized around domain objects. The memory artificial intelligence needs.
A new infrastructure category enables the data economy.
Legra is infrastructure. It connects meaning, rights, delivery, execution, evidence, and value exchange into one operating model.
Graph databases
Store, query, and reason over connected data.
See the boundaryData marketplaces and Product platforms
Describe ownership, quality, interfaces, and governed supply.
See the boundaryData spaces
Coordinate trust, policy, and exchange across organizations.
See the boundaryPersonal data pods
Separate personal data control from individual applications.
See the boundaryWorkflow platforms
Coordinate tasks, decisions, people, and systems.
See the boundaryCollaboration platforms
Capture documents, messages, meetings, and team activity.
See the boundaryIntegration platforms
Connect applications, transform payloads, and orchestrate APIs.
See the boundaryBlockchains
Coordinate public state and deterministic on-chain agreements.
See the boundaryTechnical and operational evidence
Data logistics, not just storage
Branch, review, and merge graph history as normal operations.
ExploreEdge-ready replication
Encrypted replicas work close to the action, online or not.
ExploreGitHub for data
Git-like branches and full history; every commit stays queryable.
ExploreWorkspace events and provenance
Every workspace journals its events as encrypted, replicated provenance.
ExploreAgent-safe operating model
Agents work through named stories on branches.
ExploreDeductive AI for property graphs
RDFS, OWL-RL, and Datalog reasoning serve Cypher and GQL users too.
ExploreInference and search together
Inference, vector search, and full-text search share one graph.
ExploreGoverned Data Products
Workspaces package owned knowledge with provenance, policies, and terms.
ExploreTrust without a chain
Content addressing, signatures, and encryption provide integrity.
ExploreOne system, five inseparable jobs.
Meaning, logistics, economics, AI work, and sovereignty operate as one system.
Graph substrate
Shared identifiers, semantics, inference, and search across sovereign workspaces.
ExploreData-logistics substrate
Storage, custody, replication, versioning, and rights.
ExploreEconomic substrate
Data value, resource costs, and multidirectional settlement.
ExploreAI substrate
A living corpus that humans and agents improve under review.
ExploreSovereign substrate
Owner-operated workspaces with selective network participation.
Explore
The strategy, one idea at a time.
The architecture behind data logistics and governed agentic work.
