Workspace
`0.2.0` is the primary Rust workspace/compiler package version.
Project status
Implementation state is not the same thing as release maturity.
Aura is an active, pre-stable language platform. The repository contains several version namespaces and historical milestone labels, so the public site reconciles workspace version, edition, component versions and roadmap status rather than collapsing them into one misleading number.
Version reconciliation
Four different things can all carry a version.
Edition
`2026` is a language syntax/feature compatibility namespace.
Components
Individual tools can carry independent versions such as `aura-pkg 1.0.0`.
Milestones
Historical “v0.3” / “v1.0” documents describe planning or subsystem progress, not one stable GA release.
Capability matrix
What exists, what evolves, what is gated.
SurfaceStatusMeaning
Language frontendCode-backedlexer, parser, AST, semantic core, Aura IR
Z3 verificationFeature-gatedverify path, solver profiles, counterexample mapping
AVMCode-backeddevelopment VM / interpreter
C backendCode-backeddefault C-oriented backend surface
LLVM IR backendEvolvingimplemented + feature-gated; not finished optimizer
Hybrid selectorCode-backedautomatic AVM→LLVM promotion not implemented
Package managerCode-backedresolver/cache/lockfile/security/signing
Sentinel + LSPCode-backedproof protocol, diagnostics, IDE integrations
LuminaEvolvingsubstantial UI/application plugin
AndroidIntegrated pathSDK/NDK, runtime cross-build, sample APK tooling
Public claims
Precision is part of the product.
Supported
- Proof-driven systems programming language
- Z3-backed verification
- Structured counterexample mapping
- AVM + C-oriented execution paths
- Feature-gated evolving LLVM IR backend
- 22-member Rust language-platform workspace
- Sentinel / LSP proof tooling
- Package, FFI, plugin and Android integration work
Not claimed today
- Formally verified compiler
- Frozen stable v1.0 language semantics
- Universal memory-safety guarantee
- Production JIT / automatic AVM → LLVM promotion
- Guaranteed <200ms proof latency across workloads
- Universal production-ready Android support
Performance
<200ms is an engineering target until a benchmark artifact says otherwise.
The repository contains caching, profiling and tuning infrastructure, and historical planning documents define interactive proof-latency ambitions. The website does not convert those implementation efforts into universal measured performance. A headline benchmark should include commit, hardware/software environment, workload, cache state, solver version/config, sample count and percentile methodology.