Repository navigation
August 1.0
August compiles readable, checked programs to native code through LLVM. The same source produces a human-readable specification and linked diagrams, from folder data flow to operation sequences. The editor uses those checked contracts for navigation, completion, diagnostics and inferred contract hints.
The 1.x compatibility contract covers accepted source behavior, documented CLI and project files, first-party package versions, and the public native ABI. Supported hosts are macOS 14 or later on ARM64 and GNU/Linux ARM64 or x86-64 with glibc 2.36 or later. Node.js 24 or later is required. Ordinary builds download verified compiler/runtime packs and native package artifacts; users do not install LLVM, Clang or an SDK.
Start a project
npm install --global @greenpandastudios/aug-cli
aug init my-app
cd my-app
aug run
aug test
aug specThe starter contains a greeting function and its same-file test. The getting-started guide introduces imports, labeled calls, testing and compiled specifications. The package guide explains public repository imports and exact dependency locks.
Workers run copied values on multiple cores with an isolated heap per worker. Native package imports use the target C ABI with checked ownership descriptors. Separate public packages exercise real LibTorch CPU tensors, SQLite, zlib and Rust BLAKE3; PostgreSQL and the macOS Metal GPU package have their own platform and library contracts.
Qualification and limits
The release qualification checks all three supported hosts, clean consumers without native tools, 0.23-to-1.0 upgrades, the exact release VSIX on two supported VS Code versions, language conformance, lifecycle cleanup, worker sanitizers, safety gyms and frozen performance limits. Passing these finite checks does not prove arbitrary programs or external native libraries safe.
Windows, musl, cross compilation, channels, inbound streaming and CUDA artifacts are outside this release. The OpenID Connect example is a demonstration with in-memory credentials and sessions. Library limits, performance results and compatibility describe the supported scope.
The offline wiki preserves the qualified source snapshot with documentation navigation corrections. Its docs-provenance.json records the compiler and documentation revisions separately. Use the online guides for current installation instructions.