This release is a pre-release and may not be stable for production use.
Automo
Automo is a deterministic framework for model research, evaluation, lifecycle management, and bounded automated optimisation. It is designed for ordinary supervised models, custom training pipelines, structured outputs, and composable model graphs without requiring domain-specific logic in the core package.
Automo owns the reusable research machinery: data snapshots and partitions, fit/validation/OOS governance, model lineage, calibration lineage, model pools, refresh evaluation, bounded research, cross-fitted model graphs, and immutable evidence. Project packages provide the thin domain layer: data sources, features, model trainers, evaluators, and optional external services.
GetDone integration is optional. Automo runs standalone.
Install
python -m pip install automo
For first-time local development, use the uv repository bootstrap:
python scripts/init_dev.py
uv run pre-commit run --all-files --show-diff-on-failure
The bootstrap installs uv with the currently selected Python when it is missing, syncs the project environment from pyproject.toml, and installs the standard clone-local pre-commit hook. uv owns Python/environment/dependency execution for development. Ordinary git commit runs the repository hooks plus the always-run pytest unit-test hook. The explicit local full-repository gate is uv run pre-commit run --all-files --show-diff-on-failure, which matches the GitHub quality job; GitHub separately runs pytest on Python 3.11, 3.12, and 3.13.
Start a project
automo init --root my-project
cd my-project
automo validate
automo doctor
automo init creates a minimal automo.toml and automo_project.py. Add your data sources, features, models, trainers, evaluators, and services to that project plugin.
Core workflows
automo status
automo plan
automo run
automo validate
automo models --help
automo refresh --help
automo research --help
Refresh uses explicit fit/validation/refresh-OOS partitions when fitted state changes. Data does not need a datetime column: predefined, stable-hash, grouped, ordered-ID, and temporal split strategies are supported.
Custom ModelTrainer hooks can fully control fitting, including delegation to external packages or services. Model graphs can consume outputs from upstream models; downstream/meta-model fitting uses cross-fitted upstream predictions to avoid stacking leakage.
Learn by example
Small synthetic examples are under examples/:
basic-supervised— built-in tabular regression path.custom-trainer— delegate fitting to an injected service.meta-model— leakage-safe stacking with cross-fitted upstream outputs.structured-output— arbitrary structured model outputs.id-only-data— deterministic splitting without timestamps.end-to-end— a compact project/runtime/registry walkthrough.
Start with Getting started, then see Agent research guidance, Public API, Trainers and graphs, Model registry, Refresh, and Bounded research.
Alpha status
0.3.0a1 is the first intentionally public alpha. Persistent public artifacts carry an artifact type and schema version, but APIs may still evolve during the alpha series. See the public alpha release contract for supported boundaries and known limitations.
Security
Automo does not sandbox project plugins, trainers, evaluators, codecs, calibrators, injected services, or delegated workflow providers. Only run trusted extension code and load trusted model artifacts. See SECURITY.md.
Development workflow
This repository uses uv plus pre-commit as the development gate. Repository/configuration hygiene, Ruff formatting/linting, and uv run pytest -q run through the uv-managed project environment. GitHub uses uv for the same gate and separately runs pytest on Python 3.11, 3.12, and 3.13. GetDone project records under .agent/ are development metadata for this repository and are not required at runtime.
Project-specific research guidance
Keep mutable research state under .automo/ and project-owned agent instructions under .project-agent/automo/. automo guidance discovers .project-agent/automo/index.json additively by default; use --no-project-agent for canonical Automo-only guidance. Pin a reviewed composition with automo guidance-lock --write and verify it with automo guidance-check. Project guidance may strengthen or specialize research rules but cannot replace protected sealed-OOS, bounded-search, evidence, or milestone-governance rules.
Metadata
Release files for automo 0.3.0a1
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 | |
|---|---|---|---|---|
| automo-0.3.0a1.tar.gz | 81.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| automo-0.3.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 198.1 kB
Release files / automo-0.3.0a1.tar.gz
| Download URL | automo-0.3.0a1.tar.gz |
|---|---|
| Size | 81.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce2a115f46349fa0ea28f949cf91fb97554ab9f6081e25a647190d638beb7333
|
|
BLAKE2b-256 checksum How to use checksums |
f756b6cfd0bd8d32d0896d8f2de970edef384f2b8c8e84c04e47f270012b473f
|
| 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 Aug 17, 2026.
Transparency logRelease files / automo-0.3.0a1-py3-none-any.whl
| Download URL | automo-0.3.0a1-py3-none-any.whl |
|---|---|
| Size | 116.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
073946c7198d381c1e6b815d1df60911904a142892427fc20e7ce178ce83de93
|
|
BLAKE2b-256 checksum How to use checksums |
d67d5aa09150f84fca8ed4208a9ed5f556e45700f6d14d24c12b775a171ddef0
|
| 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 Aug 17, 2026.
Transparency logSecurity for automo 0.3.0a1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for automo-0.3.0a1.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 Aug 17, 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.