REPL & AVM

Aura’s development execution model and why it remains distinct from native-oriented backends.

aura-interpret provides Aura’s development VM/interpreter path and debugging infrastructure.

Run

cargo run -p aura -- run main.aura

The primary CLI exposes modes including avm, llvm and hybrid.

What AVM is for

The AVM is the low-friction development path. It is useful for:

• fast edit/run iteration,
• development execution,
• debugger integration,
• serving as one execution surface for compatibility/differential work.

What hybrid is not

Current source explicitly says automatic promotion from AVM execution into LLVM inside the AVM is not yet implemented.

Therefore:

hybrid selector ≠ production JIT

until an actual promotion path exists and is tested.

Native paths

C-oriented and LLVM IR backends remain separate compiler surfaces. Keeping them separate is architecturally valuable: proof results, IR validation and backend parity can be reasoned about without hiding differences behind one runtime mode.