Konjure SDK 0.1 is an early implementation. Its portable core and working website are the foundation for broader spatial applications.
| Area | Current implementation |
|---|---|
| Rust | DSL compiler, typed document validation, geometry, runtime, CLI |
| Programming language | Nominal types and receiver methods, enums and results, static body checking, traits, modules, component joins and init/frame/done system callbacks |
| Physics | Rapier sphere/box rigid bodies, fixed steps, forces, impulses and contact output in the Rust/WASM spatial runtime |
| WASM | Same compiler/runtime, generated bindings, bulk frame exports |
| Web | Interactive editor, geometry renderer, actions, receipts, local drafts and replay |
| Language workbench | Compile diagnostics, play/pause/tick step/finish, entity state, source-linked traces, builtin links and scene controls |
| Konjure Kreate | Installable standalone workshop with browser project library, source-file import/export, modules, four checked starters, offline local editing/runs after the first successful cache, and desktop/phone views |
| Blender | Blender 5.2 extension for evaluated .konjure scene snapshots, file import/export, and revision-guarded local Kreate bridge sync |
| Live pairing | Browser and native protocol clients, QR/link invitations, shared controls and source revisions, public relay with temporary durable history |
| WebXR | Capability discovery, explicit AR/VR entry, session-local hit-test placement |
| C ABI / Python | Native library, explicit handles/buffers, Python consumer and executable tests |
| Unity | UPM package and native adapter; Unity 2022.3 Editor executed native compile/sample/dispatch/dispose; rendered player/device acceptance remains |
| Embedded | Precompiled no_std + alloc runtime; Cortex-M4/M7 target compile checked; board/allocator budgets still apply |
| RayNeo | Native/wgpu app accepts SDK scenes; Android build checked; physical SDK and room-anchor acceptance tracked separately |
Deliberate boundaries
The new programming interpreter is exposed to Rust and WASM. Its Unity and Python adapters remain future work; the Blender extension exchanges evaluated snapshots, not procedural Blender authoring or execution. Statement breakpoints, media loading and capture, custom shaders, external mesh loading, advanced physics and persistent XR anchors remain implementation work. See the language design and limits for the current contracts. Model-provider connections, ROS 2 and USD adapters are separate integrations. Conversation records are implemented; an always-listening multimodal assistant is a separate host concern.
The SDK is distributed through the project checkout. Public package registries and a stable 1.0 compatibility promise have not been released. The generated formats identify their versions so future migration can be explicit.
Evidence levels
Host tests establish behavior under their recorded conditions. A browser viewport test establishes responsive layout. A native/WASM comparison establishes agreement for the tested inputs. Physical device tests establish specific camera, session, rendering or tracking observations. These results are reported separately.