2026-09-12

Building a spatial foundation

Why Konjure starts with a Rust core, an explicit scene language and a working browser consumer.

Konjure began with hands-on experiments across a browser, native rendering and RayNeo glasses. Those experiments exposed the boundaries a reusable SDK needs: scene state, sensor evidence, model output and device effects have different owners and different lifetimes.

The new SDK puts the common semantics in Rust. Konjure DSL compiles into a validated scene document. Geometry is prepared once, behavior is sampled at explicit scene time, and input becomes a declared action with an inspectable receipt.

Build a complete path

The playground is a consumer of the SDK. Source compiles locally through Rust/WASM. Its renderer receives geometry and matrices; it does not implement a second interpretation of the language. The same document can be sampled by the native CLI and consumed through the C ABI.

That gives the project a concrete agreement to test. Native and WASM should compile the same source and evaluate the same action sequence. Invalid candidates should produce a useful diagnostic and preserve the accepted scene. A caller retrying an action because its buffer was too small should not execute that action twice.

Keep evidence attached to claims

Spatial applications are especially sensitive to false equivalences. Camera orientation is not camera-to-eye calibration. A room-anchor flag is not a tracking test. A model’s inference is not a physical action.

Konjure keeps observations, authored conversation, scene documents and effect proposals explicit. These contracts leave room for model providers, robotics adapters and simulation engines to evolve without letting their assumptions leak into every client.

A site that uses what it documents

The website uses Astro and reusable Alkemist packages. The compiler, examples and downloadable contracts come from the Rust source. Documentation and interactive scenes live together so an explanation can be exercised immediately.

This is the first SDK preview. The support status separates implemented functionality from platform checks and future modules.