Package structure
AIX keeps the package readable as a tree of concrete entries instead of collapsing everything into an opaque blob.
AIX file format
It packages pages, schema, and tools into a distributable artifact for AI agents.
Reading model
The homepage should immediately tell readers what the package contains, how those files define pages, and how schema expands that structure into runtime-facing surfaces.
AIX keeps the package readable as a tree of concrete entries instead of collapsing everything into an opaque blob.
App and page config files define navigable surfaces and carry the context needed to interpret the package.
Schema-bearing pages can be promoted into tool-facing contracts without losing the link back to the package.
How readers interpret AIX
Readers start with the package boundary and enumerate entries such as `VERSION`, `app.json`, page files, and assets.
Page config and single-file components are interpreted into page summaries, descriptions, and layout hints.
Schema data adds explicit contracts to those pages so the package becomes more than a file container.
Tool descriptions can then be generated from the same package-native structure rather than reconstructed elsewhere.
Core package
The `aix` crate defines the AIX format itself. It provides the package reading model, page analysis logic, and the structural semantics that every other tool in the repository builds on.
Use it when you need the canonical library surface for reading `.aix` packages, resolving page metadata, or deriving format-native structures in Rust.
cargo test -p aixCLI package
The `aix-cli` crate turns the format model into terminal workflows. It is the command-line entry point for packaging, validating, and inspecting `.aix` artifacts.
Use it when you want to work with AIX from automation scripts, local development, or release pipelines without embedding the format library directly.
cargo run -p aix-cli -- --helpWeb package
The `aix-web` crate makes the same format capabilities available in the browser. It exposes AIX through WASM bindings and supports interactive inspection surfaces such as the Package Lab.
Use it when AIX needs to be explored, demonstrated, or integrated into web-based environments without leaving the format model behind.
cargo check -p aix-web --target wasm32-unknown-unknownNext Step