UMF is a machine-readable model of schemas and metadata. An action describes a requested business change: its inputs, permitted access, conditions and implementation binding. Reading that description does not perform the change.
This guide starts with an order that needs approval. You do not need prior knowledge of UMF, CQRS or formal analysis. First inspect a declaration without a database. Then learn how a separate consumer executes it safely.
Run portable inspection, explain why it changes no order, identify an unsupported declaration, distinguish rollback from an uncertain result, and decide when a query is fresh enough. Native execution is an optional local exercise with Docker; it is not a hosted UMF service.
Figure V2. The library lane checks metadata. The consumer lane owns authentication and business transactions. No inspection or compatibility check invokes the consumer. Text explanation.
Install the bundled SDK from the UMF 0.10.13 release, then follow the installation and usage example. No separate actions package is needed. The SDK includes the current core format; vocabulary declarations remain explicit.