agi-app-sklearn-pipeline
agi-app-sklearn-pipeline publishes the sklearn_pipeline_project AGILAB app
as a self-contained PyPI payload. It keeps a normal scikit-learn pipeline
workflow intact while making the executable app boundary, arguments, and
evidence artifacts explicit.
Purpose
Use this package to run a compact classic ML proof: generate a deterministic
classification dataset, train a StandardScaler + LogisticRegression
pipeline, and persist the model, metrics, predictions, report, and run
manifest together.
Installed Project
The distribution name is agi-app-sklearn-pipeline; the AGILAB project name is
sklearn_pipeline_project. The package exposes both sklearn_pipeline and
sklearn_pipeline_project through the agilab.apps entry point group, so
AgiEnv(app="sklearn_pipeline_project") resolves the project without a
monorepo checkout.
Install
pip install agi-app-sklearn-pipeline
The app project installs scikit-learn when AGILAB prepares its project environment. The payload package stays lightweight and only exposes the project root.
Run In AGILAB
Select sklearn_pipeline_project, then open ORCHESTRATE. Keep the defaults,
run Deploy scheduler & workers, then run RUN. The worker exports model quality evidence and a
manifest under sklearn_pipeline/evidence.
Expected Inputs
The default run generates a synthetic dataset with
sklearn.datasets.make_classification. No external dataset, API key, notebook,
cloud service, or private model is required.
Expected Outputs
The worker writes metrics.json, predictions.csv, model.joblib,
sklearn_report.md, run_manifest.json, and sklearn_pipeline_summary.json.
Change One Thing
Change regularization_c from 1.0 to 0.5, then rerun the app. The manifest
and metrics artifacts should make the changed behavior auditable.
Scope
This is a reproducible scikit-learn app example. It is not a generic apps-page, production model registry, or serving stack. Sklearn-specific logic stays inside the app project; shared pages should only consume app-agnostic artifact contracts such as metrics, predictions, and manifests.
Metadata
Release files for agi-app-sklearn-pipeline 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_sklearn_pipeline-2026.10.10.1.tar.gz | 17.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agi_app_sklearn_pipeline-2026.10.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.8 kB
Release files / agi_app_sklearn_pipeline-2026.10.10.1.tar.gz
| Download URL | agi_app_sklearn_pipeline-2026.10.10.1.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e81d9c0e24070a82036d10310a3f3da32e3cc4e5fa39fb6cbc6b67beead20771
|
|
BLAKE2b-256 checksum How to use checksums |
fbaf1dc50da0ed6b0bbcd7f1fae1521082481d53792642e7fbdedefc039146cd
|
| 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_sklearn_pipeline-2026.10.10.1-py3-none-any.whl
| Download URL | agi_app_sklearn_pipeline-2026.10.10.1-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c28d4888af6a2c593b8bf9ee5c35935ad0b3d4776e2f170052b5155d1523fb6
|
|
BLAKE2b-256 checksum How to use checksums |
01d90cf254273d402bf976e1cc81f7f8a82f5f020e613f29d4540dc4db1924dc
|
| 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