Project and packages
AGILab components
The public distribution is split into install surfaces, runtime components,
and payload bundles. agilab is the product entry point, agi-core is the
compact Python/runtime API, and the remaining packages are published so
releases can install only the pieces they need. See
Package publishing policy for the release and versioning contract.
Read the repository and package split as three planes:
Control plane: product entry points, runtime APIs, environment resolution, worker packaging, and local/distributed execution.
Payload plane: apps, page bundles, templates, notebooks, examples, and PyPI payload umbrellas.
Evidence plane: proof, audits, release contracts, supply-chain evidence, UI robot outputs, docs mirror, and agent/runbook automation.
The three planes are released together so users can install a bounded runtime while maintainers can prove the matching payload and evidence contracts.
Package |
Role |
Typical installer |
|---|---|---|
Product CLI, UI shell, and public extras. |
|
|
Compact Python API and matched runtime stack. |
|
|
Environment, settings, paths, and artifacts. |
Pulled by runtime installs. |
|
Worker classes, dispatch, and build hooks. |
Pulled by worker installs. |
|
Local, Dask, SSH, and install/run APIs. |
Pulled by |
|
Streamlit page and widget helpers. |
Pulled by |
|
Portable web component contracts for rich UI islands. |
Pulled by |
|
Umbrella for public analysis page bundles. |
Pulled by |
|
Umbrella for public app packages and catalog metadata. |
Pulled by |
Per-app packages such as agi-app-flight-telemetry and page bundles such as
agi-page-geospatial-map are payload packages behind the agi-apps and agi-pages
umbrellas. They are published separately so app/page payloads can evolve
without forcing every runtime component to carry those assets.