Release and development status

Aner has no publicly released native runtime or VS Code extension yet. The website publishes documentation, example source and notebooks. Those materials do not include an installable interpreter or VSIX, and a development version number is not public release evidence.

Three distinct statuses

Status	Meaning	What it does not establish
Released	A public native or editor artifact is explicitly published with its version, platform requirements and integrity information.	Publishing a guide, source example, screenshot or benchmark alone does not release software. No public runtime or VSIX currently meets this status.
Implemented in development	The current development implementation supports the documented API, subject to its tests, resource limits and actual compiled backends.	It does not mean a public download exists, every platform is supported, or every privately provided executable includes that API.
Planned / Design	A proposed capability or direction remains future work; a design document may also discuss current implementation notes.	A roadmap entry, illustrative signature or architectural diagram is not an implemented or released feature.

Implementation and publication are separate decisions. Features can be implemented and verified internally while their runtime and editor artifacts remain unpublished. Internal verification does not change public availability. The --prod flag selects execution without automatic development recording; it is not a public release channel. Likewise, a C++/CMake Release build selects optimization settings, not publication. Successful production mode execution or an optimized build does not supply public release evidence.

Public availability

All native platform entries on Downloads are currently In preparation. No public Aner VSIX or Marketplace release is available. Read the target entry itself when availability changes; do not infer an installable package from a module card, a version printed by a source build or a compatible editor helper.

The language and module references, examples and roadmap describe development behavior and future work. Source/API milestone numbers in those materials identify compatibility or historical development; they do not establish publicly released versions. Existing recorded results remain evidence for their exact source, build, data and hardware, rather than for an unspecified public binary.

A public release would need an actual published artifact and version, its verified operating system/architecture scope, checksum and size, runtime dependencies, installation information, and compatibility notes. Native runtime and editor availability must be identified separately. Public source access and licensing also require their own explicit publication; a website code sample is not a public runtime source distribution.

Reading a development reference

An implementation statement describes an API contract in the development engine. Check its imports, exact argument labels, types, shapes, missing data rules, limits and errors. Native database clients, TLS runtimes and accelerators are optional build/runtime dependencies; a documented API does not make an unavailable client or device present.

Complete example source and notebook downloads may be inspected without an interpreter. Executing them requires compatible native tooling already supplied privately or built from source. Notebook execution also requires a compatible development extension or separately configured kernel. Follow installation prerequisites, supplied archive verification and the development VS Code guide if you have such tooling.

Planned capabilities remain separate from implemented development behavior. Preserve existing caveats about cooperative deadlines, bounded memory, incomplete previews, explicit scientific units, uncertainty models, supported model families and operation specific backends. A release status label does not broaden any of those contracts.