Axios Documentation

Overview of the Axios monorepo projects, including the Atom protocol, Eos build scheduler, and Ion CLI

[!WARNING] Axios is in early-stage active development. Specifications, protocols, and APIs are pre-1.0 and will change.

New here? Start with the FAQ — the whole project explained in one place: what Axios is, why it matters, how each layer works, and how to get involved.

Axios is a set of independent projects for decentralized source publishing, hermetic builds, and package management. The stack has six layers and a utility crate:

  1. L0: Cyphr — Signing and message-digest primitives (Coz), external to this repository; every layer above signs and verifies through it.
  2. L1: Atom (atom/) — Content-addressed source publishing protocol. Core identity (atom-id), protocol traits (atom-core), URI parsing (atom-uri), and the Git backend (atom-git) are implemented with tests and fuzz harnesses.
  3. L2: HTC (Hermetic Transactional Composition) — The post-Nix build substrate: upstream's own build, run inside a cryptographic closure, with no expression language and no store-path lore. Decided in ADR-0005 and elaborated in the HTC SAD; no crates exist yet, implementation is future work.
  4. L3: Eos (eos/) — The atom-DAG build scheduler. Scheduler traits (eos-core) exist; the eos-snix build engine is pre-substrate code slated for removal — the evaluator is deleted from the design (ADR-0006) — with the executor re-cut around HTC's trait pending. The daemon (eos-daemon) and Cap'n Proto RPC protocol (eos-proto) are under development.
  5. L4: Ion (ion/) — User-facing CLI, manifest schema, and dependency resolver. Manifest parsing (ion-manifest), lockfile schema (ion-lock), and the Eos bridge (ion-eos) are prototyped with fuzz harnesses. The resolver (ion-resolve) and CLI (ion-cli) are under construction.
  6. L5: Plugins — Ecosystem adapters (Cargo, npm, PyPI, …) using Atom and Ion as a publishing overlay; not yet built.
  • alurl — URL alias resolution, used by atom-uri to expand shorthand source identifiers like +gh/owner/repo.

Sections

  • Explanations — Architecture, security model, and ecosystem integration.
  • How-to guides — Step-by-step instructions for contributors and operators.
  • Reference — Specifications, schemas, and spec compliance tracking.
  • Architecture — System design, blueprints, and decision records.