Ecosystem

The product surface around the compiler already exists.

Aura includes package management, an SDK, standard library, language server, Sentinel, FFI, Nexus plugins, Lumina, domain integrations and Android/release tooling. Each is presented with its real implementation status, not as a frozen platform guarantee.

Sentinel

An editor built around proof feedback, not just syntax highlighting.

`editors/sentinel-app` is a Tauri 2 + CodeMirror application. Aura’s language server owns proof streaming, structured diagnostics, counterexample transport, caches and debugger/performance integration so Sentinel can render language-specific workflows.

Proof phasesNon-blocking custom LSP stream states.
Counterexample UXStructured payloads instead of parsing raw solver text.
Debug pathAVM/native-oriented debugging infrastructure lives in the platform.
Protocol surface

Aura protocol v1

aura/proofsStreamStart
aura/proofsStreamCancel

start → phase(parse)
      → phase(sema)
      → phase(normalize)
      → phase(z3)
      → done | error | cancelled

Aura-specific protocol compatibility is versioned independently from standard LSP behavior.

Packages

A package system with integrity and signing primitives.

`aura-pkg` contains cache, registry, resolver, lockfile, security, signing, metadata and command modules. Documentation historically describes more commands than the executable surface; this site lists only code-backed operations.

Standalone `aura-pkg`

initCurrent standalone command surface.
addCurrent standalone command surface.
removeCurrent standalone command surface.
listCurrent standalone command surface.
publishCurrent standalone command surface.
verifyCurrent standalone command surface.

Supply-chain building blocks

  • SHA-256 integrity
  • SemVer-oriented resolution
  • artifact download/cache
  • lockfile state
  • optional Ed25519 signing

Public registry uptime/SLA is not claimed without operational evidence.

Nexus

Domain features do not all have to become core syntax.

aura-nexus

workspace

Plugin manifest/integration layer that can participate in build and verification paths.

aura-plugin-ai

optional

AI-domain integration surface backed by a real workspace component; capability claims remain example/module-specific.

aura-plugin-iot

optional

IoT-oriented extension path with verifier-related feature integration.

Lumina

An application layer growing beside the core language.

Lumina is a substantial plugin, not a mockup: the repo contains Raylib support, layout/render syntax, input handling, TextInput, Box, grid work, image fit and audio controls plus real examples. It remains an evolving application/UI layer rather than a frozen cross-platform GUI contract.

Current vertical slice

import aura::lumina

cell main():
    layout:
        Grid(columns: 2, gap: 16) {
            render: Box(...)
            render: Button(label: "Play") {
                on_click: ~> { ... }
            }
        }

Repository-backed work

  • Raylib-backed rendering feature
  • layout primitives and styling
  • interactive input + TextInput
  • Box and grid layout
  • image fit modes
  • audio controls and examples
See repository examples
Android

A real integration path, not a universal platform promise.

SDK / NDK

Setup automation prepares Android toolchains used by the repository workflow.

Runtime cross-build

`aura-rt` is exercised for aarch64-linux-android and armv7-linux-androideabi paths in CI.

APK workflow

Sample APK automation plus emulator/build helper tooling demonstrate a vertical integration slice.