agi-app-mission-decision
agi-app-mission-decision publishes the mission_decision_project AGILAB app
as a self-contained PyPI payload. It demonstrates deterministic mission
decision evidence rather than a storyboard or slide-only demo.
Purpose
Use this package to run a repeatable decision loop: load a compact mission scenario, score candidate routes, inject an event, re-plan, and export evidence that can be inspected by AGILAB analysis pages.
Installed Project
The distribution name is agi-app-mission-decision; the AGILAB project name is
mission_decision_project. The package exposes both mission_decision and
mission_decision_project through the agilab.apps entry point group, so
AgiEnv(app="mission_decision_project") works without a monorepo checkout.
Install
pip install agi-app-mission-decision
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
From the UI, select mission_decision_project, open ORCHESTRATE, then run
Deploy scheduler & workers and RUN. Open ANALYSIS with the decision-evidence page to
inspect strategy deltas and the adaptation timeline.
Expected Inputs
The packaged project includes a deterministic sample scenario. It also includes offline public macro-context fixtures so the default proof does not need a live FRED call, API key, private dataset, or network access.
Expected Outputs
The run writes scenario metrics, generated pipeline evidence, sensor streams, candidate route tables, decision timelines, and reducer summaries under the mission-decision output paths.
Change One Thing
Change a scenario constraint or event severity, then rerun the app. The final decision artifact should show whether the selected strategy and latency/cost deltas changed.
Scope
This is a deterministic R&D app for mission-decision reproducibility. It does not claim live command-and-control integration, production autonomy, or enterprise governance.
Metadata
Release files for agi-app-mission-decision 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 | |
|---|---|---|---|
| agi_app_mission_decision-2026.10.10.1.tar.gz | 23.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agi_app_mission_decision-2026.10.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.2 kB
Release files / agi_app_mission_decision-2026.10.10.1.tar.gz
| Download URL | agi_app_mission_decision-2026.10.10.1.tar.gz |
|---|---|
| Size | 23.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54c53f7ce94aa4a2e018f550b2246a77524925f0ed46caf228a298f555868aa9
|
|
BLAKE2b-256 checksum How to use checksums |
bad9bc37af3ecc6fe05a9e3c123f0a4057ff63ecb9c2aa87bb1068c57ee1c85b
|
| 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_mission_decision-2026.10.10.1-py3-none-any.whl
| Download URL | agi_app_mission_decision-2026.10.10.1-py3-none-any.whl |
|---|---|
| Size | 29.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb2833420e8e3c31f8af73acacf82495e76774573a6d3fb227891d17fc66196a
|
|
BLAKE2b-256 checksum How to use checksums |
f65f26a5f7e590c4ba0e50ea1170de470eccdf0fce89005c5900e966e13bebb0
|
| 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 log