# WRK-000C measurement handoff SQLite adoption does not close the latency ticket. This scenario prepares comparable local datasets; it makes no performance claim and was not run as a benchmark in WRK-000D. Use the same final executable/package, machine and source revision for both backends. Keep companion libraries beside the executable. ```sh python3 scripts/latency-fixture.py --binary "$PWD/build/native/package/ai-engineering" \ --directory /tmp/aie-latency-sqlite --works 100 --entries 10 --storage sqlite python3 scripts/latency-fixture.py --binary "$PWD/build/native/package/ai-engineering" \ --directory /tmp/aie-latency-legacy --works 100 --entries 10 --storage legacy ``` Directories must be new. The script creates only synthetic Works/notes, with no approval, installation or migration. `latency-fixture.json` records version, binary SHA-256, backend, environment, volume and selected Work. Creation time is distinct from query latency. Record the source revision/build identifier as well; the release label alone is insufficient to distinguish this checkout from older 0.1.0 builds. Measure fresh processes separately from repeated queries. In each dataset, repeat `work show WRK-0064 --format json`, `work context WRK-0064 --format json`, `next-actions WRK-0064 --format json`, `work list --open --format table` and `status --format json`. Capture wall time, exit status and whether the command gives feedback while waiting; avoid including terminal rendering time accidentally. Record each sample, then compare median and tail latency. Vary volume afterward (1/10/100 Works), using identical note counts and commands across both backends. Record OS/CPU, package/JVM mode, protocol/database schema and source access settings. Use no registered Git repositories first, then measure their contribution separately. Do not mix migration, integrity repair, network/provider calls or fixture generation into query timing. The current physical native verification used macOS arm64 and GraalVM CE 25.5.5.0+3 with SQLite JDBC 3.54.1.0 / sqlite3 3.54.1; other machines need their own recorded environment. WRK-000C remains OPEN until actual measurements and responsiveness criteria justify its decision and implementation.