Current Status
AiLangCore is in public beta hardening. The current beta builds are AiLang 0.0.1-beta.6, AiVM 0.0.1-beta.1, and AiVectra 0.0.1-beta.1. The project is usable for demos and early evaluation, but contracts may still change before the first stable release.
- Human install flow uses the public SDK installer.
- Agent project setup starts from
ailang init --agent codex. - Contributor work is split across AiLang, AiVM, AiVectra, packages, examples, and website repositories.
Alpha
Alpha proved the split project shape and public artifact flow. Completed alpha work made AiLangCore installable, understandable, and demoable enough to enter beta hardening.
- Separate AiLang, AiVM, and AiVectra ownership.
- Publish installable SDK artifacts.
- Define
ailang init,build,run,test, andpublishworkflows. - Prove package restore through the curated registry.
- Document native AiVM memory and syscall discipline.
- Move public examples into a dedicated examples repository.
Beta
Beta means the project is credible for outside contributors, conference demos, and sponsor review.
- Install flow is continuously verified on macOS, Linux, and Windows.
- Deterministic golden tests are stable across supported hosts.
- Native AiVM artifacts are released for supported targets.
- Package restore, package tools, and templates are documented and tested.
- Spec ownership is clear and duplicate specs are removed or replaced with pointers.
- Resource limits, error codes, and production/debug runtime behavior are stable enough for external users.
- AiVectra has a functional documented sample app with real UI validation.
Release Candidate
Release candidates are for contract freezing and packaging reliability, not architectural churn.
- Semantic specs are internally consistent.
- CLI contracts are frozen for 1.0.
- Package registry format is frozen for 1.0.
- Release automation and install/update flows are repeatable.
- Cross-platform CI and release CD are green from clean runners.
1.0
Version 1.0 is the first stable promise for project files, CLI behavior, SDK layout, package restore, and runtime contracts.
- Native AiVM is the default runtime.
- SDK layout and version selection are stable.
- Package restore is stable.
- AiVectra has a documented app model.
- Human and agent project workflows are documented.
Sponsorship Focus
Sponsorship funds CI and release automation, deterministic test coverage, cross-platform packaging, documentation, native AiVM runtime hardening, and AiVectra runtime stabilization.
- CI/build infrastructure for macOS, Linux, Windows, and future mobile targets.
- Release automation for signed, reproducible SDK and VM artifacts.
- Deterministic compiler, VM, package, and UI regression suites.
- Documentation for human developers, AI agents, and contributors.
- Native AiVM production hardening, profiling, debugging, and resource-limit work.
- AiVectra runtime validation so generated UI can be evaluated by agents and humans.
