Achronyme 0.1.0

Published features, compatibility, and production proving evidence for Achronyme 0.1.0.

Status: published stable release. Core v0.1.0, editor v0.3.0, and the 0.1.0 web service are tied to the exact source receipts below.

The 0.1.0 release is built from core revision fd07b38e16256e2ed6a8f2b438d340a681c9b0ac. It adds a host execution model with structured concurrency and explicit authority, and it changes proof generation to require an explicit source of trust.

Version matrix

The installer resolves the latest published core release from GitHub. A normal install now returns 0.1.0 and verifies its published checksum.

Structured concurrency

• concurrent { ... } creates a lexical task scope.
• spawn call(...) creates a child owned by that scope.
• await task, await task as outcome, and await [a, b] as race make joins, recoverable failures, and races explicit.
• Bounded channels, cooperative cancellation, task diagnostics, and runtime limits prevent detached or unbounded background work.

See Concurrency and Host I/O for the language and CLI contract.

Explicit host authority

File and TCP operations use owned resources. Programs receive no ambient read, write, connect, or listen access. Authority is granted with exact CLI flags or the corresponding achronyme.toml settings:

ach --allow-read ./data --allow-connect 127.0.0.1:443 run app.ach

Host effects are rejected inside prove and circuit code. The compiler keeps the external world outside the deterministic proof boundary.

Native execution

ach run supports the interpreter and LLVM 21 ORC JIT with an explicit --engine interpreter|jit|auto selector. ach aot emits a native executable against the packaged AOT runtime. Release CI covers interpreter fallback, JIT, AOT, installed layouts, resource limits, and Linux x86_64/aarch64 packaging.

Fail-closed proving trust

Proof generation no longer creates local keys implicitly:

# Development only. The output is not production trusted.
ach --insecure-dev-setup run proof.ach

# Production path. The key store must match the exact optimized circuit.
ach --trusted-key-dir ./trusted-keys run proof.ach

Production BN254 Groth16 stores bind the proving key to the R1CS, phase-1 transcript, phase-2 contributors, final public beacon, and release evidence. Detached BN254 and BLS12-381 Groth16 verification is available through ach verify. Plonkish and BLS12-381 proof generation remain development-only in this release line.

See Proof Generation for user-facing commands and the core repository’s versioned trusted-setup guide for the full operator workflow.

Editor release

Editor 0.3.0 tracks the final core revision and adds syntax and semantic highlighting for structured concurrency, task handles, owned I/O, and capability-aware builtins. It also includes Circom language activation, parser-backed diagnostics, hover, completion, document symbols, definitions, references, and rename support.

Production publication evidence

The release closed every production gate against the exact core revision:

1. an independently controlled phase-2 contribution;
2. a previously committed, publicly verifiable final beacon;
3. a final key that verifies against the exact release R1CS and phase 1;
4. successful snarkjs-to-Achronyme and Achronyme-to-snarkjs proof checks;
5. packaged release evidence with exact hashes, sizes, revision, and metrics.

The public ceremony dossier records the immutable commitment, beacon response, artifact hashes, verification logs, and measured resource use.

See the Changelog for the complete historical release record.