The language, OS and SDK evolve together.
Nexus is the native systems language and toolchain behind Frames. Nexus SDK 6.10.0 now provides the standalone compiler, project/build tooling, native Frames targets, packaging/signing, diagnostics, C/C++ interoperability and evidence tools used by the platform.
Nexus SDK 6.10.0
The current standalone SDK is Apache-2.0 licensed and contains 246 canonical source files. Local Linux x86-64 Clang and GCC certification lanes pass; the prepared external x64/ARM64 GitHub matrix remains a separate certification gate.
SDK status and exact identity →Create → Check → Build → Test → Inspect → Package → Sign.
The goal is one coherent systems-development workflow rather than stitching together unrelated compiler, package, build, signing and evidence tools.
Language + safety
Ownership/move checking, borrowing/reference rules, deterministic cleanup, explicit unsafe boundaries, effects/capabilities and broader hosted async/concurrency support.
Native Frames targets
Stable x86-64 FEX64 output, ARM64 preview output, FKRN64 kernel tooling and a Frames PE compatibility target.
Applications & packages
Build FEX executables and deterministic FAPP/FSETUP/FPKG containers, then inspect integrity and optional publisher trust.
C/C++ bridge
Hosted extern "C", conservative C bindgen, C header export and C++ bridge generation support incremental porting.
Debug + IDE
Structured diagnostics, explain codes, debug-build, profiling and machine-readable IDE information live in the SDK command surface.
Evidence tooling
SDK verification, safety reports, C++ workload comparisons, build comparisons and external certification record formats make claims auditable.
Nexus Studio remains a product-layer target.
The compiler and standalone SDK exist today; the full native Nexus Studio graphical IDE remains a later Frames desktop milestone. The SDK documentation intentionally separates implemented tooling from future graphical IDE work.
See developer roadmap