Skip to content

Bundle format

Manifest schema.

Think of the manifest as the package’s trust envelope: enough metadata to understand what it is, who owns it, what compiler produced it, and what files belong to the version.

01 · section

Key fields

The package model depends most on namespace, slug, version, description, primary language, compiler version, surface areas, tags, README, and file references.

  • namespace + slug identify the package
  • version identifies the package release
  • compiler_version ties the output back to a compiler build
  • surface_areas and tags make browse/search useful
Manifest schema · axint docs · axint registry