A process is only one view of the knowledge required to perform the work.
Workflow and BPM platforms coordinate steps, decisions, people, and systems. Legra places that execution inside a broader graph of objectives, personas, policies, data, authority, agreements, conversations, evidence, and reusable organizational knowledge.
Where this category excels
Explicit process sequencing, task assignment, approvals, and operational monitoring.
Low-code composition and integration with enterprise applications.
Repeatable automation of well-understood business procedures.
Where Legra extends the model
Use Cases remain living context boundaries rather than static process diagrams.
Stories can resolve to graph operations, agents, humans, APIs, or existing code.
Task trees and workspace journals connect execution evidence back to the objects and knowledge involved.
Questions to use in an evaluation
Can the platform represent why the process exists and what knowledge it relies on?
How are exceptions, expert learning, and agent contributions fed back into the operating model?
Can one Use Case cross organizations, sovereign workspaces, agreements, and value flows?
Beyond database features
Graph features are only the substrate.
Legra also organizes the work that uses and changes the graph, the evidence needed to review that work, and the economic relationships that move data and value between parties. That operational layer is what turns graph infrastructure into data logistics infrastructure.
A complete history of the work
Legra keeps each piece of work together with the changes it made, the evidence behind it, and any costs incurred. That history stays private to the workspace and cannot be quietly rewritten.
Work by people, AI agents, and automated services appears in one traceable record.
See what is happening now, then return to the same history later for review.
Full provenance connects signed commits and exact deltas to task and transaction lineage, actors, delegated authority, imports, and every retained rule and premise behind derived facts.
Evidence answers who or what acted, on whose authority, from which inputs, and with which result.
Commit, activity, fact-origin, and derivation evidence remains attached to the workspace and its history.
The admitted total composes independently priced data value, compute, storage, custody, transport, external I/O, rights, and operator services instead of treating bytes as the value of data.
Charges, credits, refunds, penalties, and commissions contribute to the final amount.
Zero is an explicit price through the same accounting path, including self-operated work.
Every resource-consuming operation follows one path: measure, price, authorize, execute, record, and settle. Detailed evidence stays with the workspace instead of one central billing ledger.
Tokens can flow to data owners, infrastructure and service Operators, and the NetworkOperator treasury.
The same evidence supports internal chargeback and external settlement; subscriptions supply token packages rather than feature gates.