Under the hood, across the trail.

01 / Explicit systems vocabulary

Fixed-width integers, raw pointers, slices, volatile memory, atomics, intrinsic operations and constrained inline assembly are part of the Stage-0 systems surface. Use explicit casts and the unsafe boundary for trusted low-level operations.

02 / The native entry contract

The freestanding x86-64 backend exports noqeri_entry(noqeri_abi*), not an OS process entry point. ABI v2 carries callbacks such as write and optional time/platform capabilities. An operating system, kernel or embedding host supplies the surrounding loader and ABI adapter.

int64_t noqeri_entry(const noqeri_abi* abi);

03 / FFI is versioned, but not every symbol is C ABI

Include/noqeri/abi.h describes the stable host embedding table; arbitrary Noqeri native export functions are not yet guaranteed to follow platform C calling conventions. The experimental binding generator supports scalar-friendly interfaces and needs real linker/ABI proof for broader uses.

node Tools/ffi/noqeri-bindgen.mjs examples/ffi/interface.json --out=build/ffi

04 / Networking and concurrent primitives

Lib/std has TCP/UDP, HTTP, TLS, WebSocket, channels, atomics and task utilities. Many are host extern interfaces; check actual platform binding and linkage before declaring network transport support. The native RFC6455 frame helper is not a complete WebSocket service.

05 / PGAS remains experimental

Runtime/native/pgas* and Lib/std/pgas* offer bounded distributed-index mapping, node-local operations, optional TLS and experimental remote execution under explicit limits. This is not an automatic shared-memory cluster, scheduler or fault-tolerant global transaction engine.