Packages

The official registry

pack.ael.openeng.ai will host the official packages for AEL and will open when AEL Beta 0.0.1 launches; until then there are no packages to download.

Only OpenEng will publish to the official registry; every version will be signed, and a published version will never change.

Servers and APIs

HTTP, gRPC, WebSocket and MCP
Model providers

You will choose local or cloud models: local model servers, optional packages for major cloud providers, and clients for inference endpoints you run yourself.
Caching and messaging

Optional packages will connect agents to streams, caches and message brokers.
Running your existing programs as tools
Robotics
Scientific computing
Quantum computing
All package families

Every AEL package, from OpenEng or from you, will be written in AEL and ship as compiled, verified AEL, with no bundled native code and no install scripts.
When a package talks to an outside system, such as a database, a model server, a robot or a quantum computer, it will use that system's own interface, and you will run that system.

You will build your own libraries into shareable packages that ship compiled, without your source.
You will build each of your own private packages into a single file.
You will host that file yourself: as a release download in your own GitHub or GitLab project, at any https address, or inside your project.
Your project will record the file's address and fingerprint, and AEL will refuse the file if it ever changes.
Access tokens for your private host will stay outside your project files.
The official registry will never host or list private packages.
AEL will never treat an external package as an official one, even if its name matches.

AEL will verify every package before using it, whatever its host: its fingerprint, its contents and how it was built.
One manifest and one lock file will give reproducible builds that also work offline.
Your lock file will pin the exact versions you built with, so builds repeat, even offline, and nothing will download when an app starts.
Each folder of a project will be able to add its own packages without affecting the rest.
Adding, installing, updating and removing packages will be atomic and safe to roll back, and a package will never run an install script.
You will select exactly the exports you use, and the compiler will flag selections you never use.
Only what you use will ship: an HTTP-only app will carry no gRPC or WebSocket code, and a GET-only API no POST handlers.