# Validate a RISC-V distribution

A RISC-V distribution check should identify the exact target and distinguish execution on a device from execution in an emulator. Keep build completion, process startup and SQL correctness as separate observations. The current [installation procedure](https://coordinatordb.com/docs/get-started/setup/install) does not by itself establish a cross-platform support matrix.

## Use a small deterministic request

Start the target executable with a disposable database and the supplied configuration. Run the supplied client against that server:

```sh
./coordinator client --database data --query "SELECT 7 * 6 AS answer, 'riscv' AS target FORMAT csv"
```

Expect `42,"riscv"`. Follow with an application-specific case that writes rows, reads them in a fixed order and checks the values after reopening the connection.

## Separate correctness from timing

Capture startup errors and failed queries even when an emulated environment is slow. A timeout imposed by your test runner should be reported as such; it does not prove that the SQL result was incorrect. For performance comparisons, report the execution environment and use the [workload measurement guide](https://coordinatordb.com/docs/resources/develop-contribute/contribute/profile-guided-optimization). For database and session selection, follow [deployment modes](https://coordinatordb.com/docs/get-started/about/deployment-modes).