Know where the trail ends.

01 / Current source and release status

CMakeLists.txt declares version 0.1.4. GitHub release assets and SHA digests determine what can actually be downloaded for a target. The site must not call version-policy documentation proof of available installers or signed artifacts.

02 / Stage-0 host versus native code target

The C++17 frontend can be built as a hosted CLI on supported toolchains. The existing native backend primarily emits freestanding x86-64 code exporting noqeri_entry(noqeri_abi*), not a Linux _start or automatically linked Windows/macOS app.

noqeri targets
noqeri build examples/native_hello.noqeri build/native_hello.s

03 / Policy targets are not completed emitters

Compiler/selfhost/targets.noqeri and object-format modules define Windows x86-64/ARM64, Linux x86-64/ARM64, macOS x86-64/ARM64 policies. The existence of target descriptions is not proof of working independently validated PE/ELF/Mach-O emission on each platform.

04 / NQRI bootstrap is not native self-hosting

A SHA-pinned Stage-1 compiler, Stage-2 and Stage-3 NQRI byte-equality chain executes through a C++ NQRI VM. Native compiler executable self-rebuild, independent seed trust attestation and complete cross-target native parity remain separate gates.

05 / Feature-level maturity matters

Web server actions, browser build-client, NoeSQL integrations, optional OpenCL GPU acceleration, PGAS and game tooling have different test footprints. Review actual source, prerequisites, security/performance regressions and device evidence per subsystem.