agi-app-multi-dag
agi-app-multi-dag publishes the multi_app_dag_project AGILAB app as a
self-contained PyPI payload. It is a read-only workflow-contract example rather
than a domain worker benchmark.
Purpose
Use this package to understand how AGILAB can connect several app projects with explicit artifact handoffs. The bundled DAG shows a flight stage producing a summary artifact that a weather stage can consume.
Installed Project
The distribution name is agi-app-multi-dag; the AGILAB project name is
multi_app_dag_project. The package exposes both multi_app_dag and
multi_app_dag_project through the agilab.apps entry point group, so
AgiEnv(app="multi_app_dag_project") resolves the project without a monorepo
checkout.
Install
pip install agi-app-multi-dag
Most users get this package through agi-apps, agilab[ui], or
agilab[examples]; direct installation is useful when validating one app
package in isolation.
Run In AGILAB
Select multi_app_dag_project, open WORKFLOW, choose the multi-app DAG template,
and inspect the runner-state preview. This package is primarily for workflow
review; use flight_telemetry_project or weather_forecast_project when you
want to execute concrete worker code.
Expected Inputs
The package ships a DAG template that names the producer and consumer projects. No private data, cluster, service mode, or live external service is required for the default preview.
Expected Outputs
The preview writes a runner-state JSON file under the AGILAB execution logs and renders the runnable versus blocked stages. It does not create a domain reducer artifact because it demonstrates cross-app orchestration, not a worker merge.
Change One Thing
Edit a handoff name in a copied DAG template and reload the preview. The blocked stage should make the missing artifact contract obvious before any downstream execution is attempted.
Scope
This package teaches multi-app DAG contracts. It is not a scheduler replacement, an Airflow/Kubeflow clone, or a production workflow governance layer.
Metadata
Release files for agi-app-multi-dag 2026.10.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agi_app_multi_dag-2026.10.10.1.tar.gz | 14.3 kB | With provenance | Details for agi_app_multi_dag-2026.10.10.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agi_app_multi_dag-2026.10.10.1-py3-none-any.whl | Python 3 | none | any | Details for agi_app_multi_dag-2026.10.10.1-py3-none-any.whl |
Total release size: 32.7 kB
Release files / agi_app_multi_dag-2026.10.10.1.tar.gz
| Download URL | agi_app_multi_dag-2026.10.10.1.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db9d6f3153fb5bd55c8ea291a771271a245559e0088009077f27f668dc5c0a46
|
|
BLAKE2b-256 checksum How to use checksums |
6c9bdc49cd6d5f12681b41b3afafffd99aa3f9b5c39029e4212a6c184e45246a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / agi_app_multi_dag-2026.10.10.1-py3-none-any.whl
| Download URL | agi_app_multi_dag-2026.10.10.1-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10aa7d3ef84b5e7bcfec7022d226b6be323eafef03e1d2f4ccb7f53b1a96aab4
|
|
BLAKE2b-256 checksum How to use checksums |
b2cb81a9665296d8205c4a445cbfc50c6fb79072124000dda4f6a9d7c41ce779
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logSecurity for agi-app-multi-dag 2026.10.10.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for agi_app_multi_dag-2026.10.10.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.