Optional owner-licensed QNX validation
This is an unexecuted stronger-evidence path. The working host demo and completed host tutorial do not depend on it. A successful synthetic test or dry-run does not close the native validation gate. Account, licence, VM and device operations belong to the owner. Never edit raw captures to make a check pass.
Prepare the licensed environment
Personally review the QNX Everywhere access and SDP installation instructions. Install a properly licensed QNX SDP 8.0, x86-64 compiler/debugger and image tools. Record the actual installed update and virtualization software version.
Use the supported Windows VirtualBox/VMware path, or an owner-prepared Ubuntu/QEMU environment. Consult the mkqnximage host/type table. No Windows/QEMU support is asserted. In Command Prompt, in the project root, initialize your actual SDK path:
call "C:\qnx800\qnxsdp-env.bat"
mkdir build\vm-vbox
cd build\vm-vbox
mkqnximage --type=vbox --arch=x86_64
mkqnximage --run
mkqnximage --getip
cd ..\..
Use a new directory; do not overwrite an existing VM. The path above is the documented conventional example, not a discovered installation. The owner confirms qconn/pdebug and devc-pty on the private VM using the QNX debugging guide. Do not expose the debugger endpoint publicly or change host security settings as an automated workaround.
Run, retain and check
From the initialized command window, use the actual private endpoint and installed
version note with python scripts/post_sdp.py --target and --setup-note; the full
argument format is shown by python scripts/post_sdp.py --help and the separate
native tutorial draft. The command writes a fresh evidence/local/run-... bundle.
It builds, deploys, captures, downloads, checks and fills a separate tutorial copy.
An error stops the chain and retains failure status. No saved login profile is used.
Read pipeline.json, check.json, build/build-receipt.json, toolchain.txt,
capture/platform.txt, capture/probe.log, capture/send.txt, capture/reply.txt
and comparison.html from that same run. A real success must include the same
client TID observed in SEND then REPLY to the logged, observed server PID, plus a
matching returned binary. Preserve all originals privately. The checker establishes
local consistency, not independent OS attestation.
Review the actual tutorial-filled.md and reproduce the steps on the real setup.
Record continuous target/host footage before replacing any host-only description.
Publish only reviewed source and appropriate text evidence; exclude licensed tools,
images, target executables, runtime shell copies and private transport logs. Review
the offered licence and relevant third-party rights personally before publication.