UMFDevelopersActions & workflowsReferenceActionsSchemasPlayground

Understand and use UMF actions

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.

Choose your starting point

What you will be able to do

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.

V2 · Two responsibilitiesLibrary · browser-compatible: Read a document. Register vocabulary. Inspect and compare declarations. No authentication or business writes. Explicit interpretation: Compile supported rules/selectors. Evaluate rules only with supplied state. This is separate from inspection. Consumer · host-only: Authenticate principal and service. Authorize. Freeze identities. Execute and verify under the native transaction boundary. Qualification boundary: Declared compatibility is not execution verification. Inspection does not invoke the consumer or access storage. Library · browser-compatible Read a document. Register vocabulary.Inspect and compare declarations. Noauthentication or business writes. Explicit interpretation Compile supported rules/selectors.Evaluate rules only with suppliedstate. This is separate frominspection. Consumer · host-only Authenticate principal and service.Authorize. Freeze identities. Executeand verify under the nativetransaction boundary. Qualification boundary Declared compatibility is notexecution verification. Inspectiondoes not invoke the consumer or accessstorage. V2 · Two responsibilities V2 · Two responsibilitiesLibrary · browser-compatible: Read a document. Register vocabulary. Inspect and compare declarations. No authentication or business writes. Explicit interpretation: Compile supported rules/selectors. Evaluate rules only with supplied state. This is separate from inspection. Consumer · host-only: Authenticate principal and service. Authorize. Freeze identities. Execute and verify under the native transaction boundary. Qualification boundary: Declared compatibility is not execution verification. Inspection does not invoke the consumer or access storage. Library · browser-compatible Read a document. Register vocabulary.Inspect and compare declarations. Noauthentication or business writes. Explicit interpretation Compile supported rules/selectors.Evaluate rules only with suppliedstate. This is separate frominspection. Consumer · host-only Authenticate principal and service.Authorize. Freeze identities. Executeand verify under the nativetransaction boundary. Qualification boundary Declared compatibility is notexecution verification. Inspectiondoes not invoke the consumer or accessstorage. V2 · Two responsibilities
Concept-map presentation · original panel text retained. Visual source and rendering limits · Mobile source

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.