runD documentation

From first result to the right execution shape.

Install the verified Darwin SDK, run one checked Flow, then use the exact guide for numerics, execution, replay, performance, or runtime integration.

PATH 01 · RUN

Run the first Flow

Verify the release, install the exact prefix, build the checked program, and assert its output.

PATH 02 · FIX

Resolve a failed setup

Match verifier, CMake, host-tuple, backend, or execution failures to a concrete remedy.

PATH 03 · UNDERSTAND

Understand the guarantee

See exactly which numbers, graph rules, ordering laws, and failure boundaries make the bits match.

Use the docs by task

Open only what you need next.

These pages are the public learning and integration authority. Repository contracts remain available as optional engineering evidence, not required continuation.

Compute

Shape one Flow

Understand Flow, Program, Job, resident execution, Batch, and Pipeline boundaries.

Read Compute

Replay

Make inputs canonical

Keep Live, Record, Replay, and Scenario on one application-owned input path.

Read Replay

Performance

Measure the boundary

Use the offload cost model and checked observations without turning them into folklore.

Read Performance

Platforms

See what ships today

Separate supported release tuples from validated candidates and future backend work.

Read Platforms

Reference

Find an API or failure

Choose a direct header, the correct result authority, and the next action for an error.

Open API & Errors

Runtime

Integrate the rest of the SDK

Use Session, Tasks, Host, Network, Storage, Telemetry, and optional Cluster APIs.

Read Runtime

Numerics

Choose the number system

Separate Compute Fixed, Math32, Math64, and portable numeric evidence.

Read Numerics

Help

Fix the first failed boundary

Preserve the typed result and resolve install, link, tuple, capacity, or backend errors.

Open Troubleshooting

Recommended order

Stop reading when your next decision is clear.

Start with a successful result. Learn the contract before adding another target, then choose and measure only the execution shape your application will use.

Run Quick Start exit 0

Understand Determinism + Numerics scope fixed

Shape Compute + Runtime cost chosen

Measure Performance + Platforms claim scoped