UMA portability lab tutorial

This tutorial proves portability through observable behavior. The native runner and WASI runner emit the same image.analyzed payload while target-specific telemetry remains explicit.

By Enrico Piovesan Updated June 22, 2026

Tutorial route

Use the links up front so the portability path feels like a guided sequence instead of a footer scavenger hunt.

Open source folder All UMA examples Previous: Post Fetcher Runtime Next: Metadata Orchestration

What you will learn

how one contract drives native and WASI execution
why parity should be checked through emitted events
how native-only capabilities stay outside the portable path

Prerequisites

Rust 1.77 or newer
rustup target add wasm32-wasip1
Wasmtime 20 or newer
jq

Run this setup command before the lab if your machine does not already have the target installed.

rustup target add wasm32-wasip1

Full tutorial

Enter the example
```
cd chapter-06-portability-lab
```
List the guided labs
```
./scripts/list_labs.sh
```

Compare native and WASI events

./scripts/run_lab.sh lab1-native-wasm-parity

Compute shared payload digests

./scripts/run_lab.sh lab2-shared-payload-digest

Exercise failure paths and capability gates

./scripts/run_lab.sh lab3-failure-paths-and-capability-gates

Check Rust and TypeScript reference parity

./scripts/run_lab.sh lab4-rust-ts-reference-parity

Run the chapter smoke path
```
./scripts/smoke_portability_labs.sh
```

What to inspect

After each command, look for these proof points. They are the signals that connect the code example back to the UMA architecture claim.

identical image.analyzed payloads
matching shared payload digests
gpu.telemetry.reported only on the native path

Acceptance check

The chapter-level validation path is:

./scripts/smoke_portability_labs.sh

Return to the repository root for the final acceptance gate:

cd ..
./scripts/smoke_reader_paths.sh

Where to go next

Chapter 7 uses contracts and events to create orchestration.

Open source folder All UMA examples Read Chapter 7: WebAssembly Portability → Previous: Post Fetcher Runtime Next: Metadata Orchestration