urma-runtime
The publication and recovery layer between records and networks.
crates.io · API reference · Source · URMA
Use urma-runtime when an application needs to plan, publish, observe or recover URMA content. It composes record codecs, identity signing, funding and network transports while keeping preparation separate from submission.
Get started
API guide
| Entry point | Use it for |
|---|---|
plan |
Publication plans, budgets and validation. |
publication |
Atomic public-record transaction preparation. |
publish |
Publication execution and progress. |
disk_plan |
Disk-backed plans for larger publications. |
disk_publish |
Execution of disk-backed publications. |
source |
Sources of records and transaction evidence. |
recovery |
Recovery of published content. |
journal |
Publication state retained across attempts. |
node |
The node-facing runtime interface. |
Where it fits
A typical application prepares and reviews a plan, approves its funding and fees, then publishes while retaining the plan and journal for recovery or continuation. urma-git, urma-files and urma-cli compose these primitives into user workflows.
Boundaries
Network calls and publication can have external effects and incur fees. Preserve the prepared transaction identity and progress state when resuming work. A successful submission and a confirmed publication are different states; use the observation and recovery APIs for evidence.
License
0BSD. Part of the URMA workspace, maintained by Zmole Cristian. Project contact.