An ecosystem others can build on
Design stable library boundaries, package identity, and documentation that grows with the language.
Seven modules currently ship inside the native Aner executable. A public package registry, independent package versions, imports of modules defined by users, and registration of models provided by others are not implemented.
The design for the long term needs clear public exports, version and compatibility rules, reproducible dependency resolution, and a stable boundary for native extensions. Numerical interoperability should preserve dtype, shape, ownership, and lifetime contracts.
This website separates current APIs, design proposals, examples, and release metadata so contributors can review the existing behavior and the proposed next step independently. A public source repository and software license still need to be finalized before the open source release.
Help investigate this question.
Bring evidence, experience, or a workflow we should understand.