<!-- Explore -->
# Current implementation line and supporting repositories.
AEON 0.9.3 is the current AltoPelago implementation line for the TypeScript packages and the related implementation work across Rust, Python, PHP, examples, tooling, and browser surfaces.
Use this page as a quick map for the public repositories around the implementation. The formal language specifications and CTS live with Aeonite; the implementation packages and learning surfaces live here.
[View npm packages](https://www.npmjs.com/search?q=%40altopelago%2Faeon)
[Open implementation repo](https://github.com/AltoPelago/aeon)
<!-- Release Line -->
## 0.9.3 at a glance.
### AEON 0.9.3
_Current Version_
Latest release line for the npm package set and matching implementation hardening work. Use this version when following the current public examples.
[View releases](https://github.com/AltoPelago/aeon/tags)
### TypeScript packages
_Package Family_
Lexer, parser, AES, canonicalization, finalization, AEOS validation, runtime, SDK, CLI, Tonic, and WebAssembly package surfaces under the @altopelago scope.
[Open npm scope](https://www.npmjs.com/org/altopelago)
### Aeonite AEON specs
_Specification Target_
The implementation follows the public Aeonite specification and conformance repositories rather than treating implementation behavior as the authority.
[Open specs](https://aeonite.org/specifications.php)
<!-- Implementation Repositories -->
## Implementation repositories are split by language runtime.
These repositories are where AEON behavior becomes executable code. They track the Aeonite specs and CTS while exposing practical package surfaces for application builders.
- **TypeScript** AltoPelago/aeon contains the current npm package line: lexer, parser, AES, AEOS, canonicalization, finalization, runtime, SDK, CLI, LSP, WebAssembly, tests, and release plumbing.
- **Rust** Rust work lives with the main implementation effort as a lower-level implementation surface for parser/runtime parity, conformance exploration, and future systems integration.
- **Python** Python work is tracked as an implementation surface for scripting, examples, data workflows, and cross-language conformance checks.
- **PHP** AltoPelago/aeon-php covers PHP lexer, parser, core behavior, AEOS, Tonic, CTS integration, and PHP application surfaces.
[TypeScript, Rust, Python](https://github.com/AltoPelago/aeon)
[PHP implementation](https://github.com/AltoPelago/aeon-php)
<!-- Helper Repositories -->
## Helper repositories support learning, authoring, and inspection.
These repositories are not separate language definitions. They provide examples, editor support, grammar assets, converters, web highlighting, materialization experiments, and learning surfaces around the implementation line.
<!-- Example Repo -->
## AltoPelago/aeon-examples
Example projects show how AEON is used from application code and small demos.
- **Runtime examples** Small projects for TypeScript, Python, and Rust surfaces that demonstrate common parsing, validation, and runtime flows.
- **Schema examples** Shared schemas and validation fixtures for reference-safe documents and browser-facing demos.
- **Starter integrations** Compact examples intended to help a new adopter move from inspection to application code.
[Open examples](https://github.com/AltoPelago/aeon-examples)
<!-- Tooling Repo -->
## AltoPelago/aeon-tooling
Tooling helps people author, highlight, inspect, and package AEON outside the runtime itself.
- **Editor support** VS Code language extension, theme, grammar, diagnostics wiring, and bundled language-server packaging.
- **Grammar assets** Tree-sitter work and syntax grammar assets for editor and tooling integrations.
- **Web and conversion tools** Web highlighter, markdown-to-&ND converter, package scripts, and authoring utilities.
[Open tooling](https://github.com/AltoPelago/aeon-tooling)
<!-- Tonics Repo -->
## AltoPelago/aeon-tonics
Tonic work sits above transport-level AEON and explores trusted materialization conventions.
- **Materialization conventions** Conventions for turning validated AEON into trusted runtime or output forms.
- **Trusted output experiments** Experiments around how consumers accept, transform, and emit materialized data.
- **Examples above Core** Examples that deliberately sit above the core notation layer without redefining AEON itself.
[Open Tonic work](https://github.com/AltoPelago/aeon-tonics)
<!-- Conformance -->
## The specs and CTS define the shared target.
Conformance work lives under Aeonite so implementation behavior can be checked against an independent specification and test surface. AltoPelago implementations should follow these repositories rather than becoming the authority themselves.
- **aeonite-org/aeonite-specs** Specification source for AEON, AEOS, NEON, &ND, contracts, conventions, drafts, and supporting language artifacts.
- **aeonite-org/aeonite-cts** Conformance test suite used to compare implementations and keep behavior aligned across runtimes.
[Open specs repo](https://github.com/aeonite-org/aeonite-specs)
[Open CTS](https://github.com/aeonite-org/aeonite-cts)