Altar Cherimoya binding
altar-cherimoya is the lightweight control-plane binding between Altar and the Cherimoya variant-effect
runtime. Installing it registers CHERIMOYA in the canonical altar.model_plugins discovery group.
The binding owns Cherimoya's artifact schema, score schema, prioritization predicate, resource requests, and
backend-neutral container plan. It does not import PyTorch, Cherimoya, a model registry, object-storage SDK,
or compute-provider SDK. The heavyweight cherimoya-score CLI and independently locked image live under
runtimes/cherimoya in this repository.
pip install altar-cherimoya
from altar.models import get_model_plugin
plugin = get_model_plugin("CHERIMOYA")
CherimoyaConfiguration.image defaults to the immutable runtime digest tested with the installed binding.
Callers may override it with another name@sha256:<digest> image reference; mutable tags remain invalid. Its
weights tuple contains one generic ResourceReference per fold, each with a required SHA-256 digest. The
URI may be local, HTTPS, GCS, S3, Hugging Face, or any other location understood by the selected storage
adapter. The digest, not the location, defines scientific identity. Mutable images and unidentified weight
bytes fail validation before a plan can be built.
The binding emits one GPU scoring task per weight resource followed by one CPU summarize task. Every weight is staged to a stable logical path, and the runtime receives only that mounted path and expected digest. It does not download weights or know which provider stored them.
The runtime streams large variant files in fixed outer batches and validates CATv1's single-track output
contract. profile_l1 is defined over softmax-normalized profile distributions.
The tests compose altar.testing.ModelResultContract and ContainerScorerContract and fake only the outer
Modal and Kubernetes clients, so they verify both result semantics and the plan/fan-in contract without an
ML framework, cloud account, cluster, GPU, or image pull.
Metadata
Release files for altar-cherimoya 0.3.0
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 |
|---|---|---|---|---|
| altar_cherimoya-0.3.0.tar.gz | 27.7 kB | Without provenance | Details for altar_cherimoya-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| altar_cherimoya-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for altar_cherimoya-0.3.0-py3-none-any.whl |
Total release size: 39.6 kB
Release files / altar_cherimoya-0.3.0.tar.gz
| Download URL | altar_cherimoya-0.3.0.tar.gz |
|---|---|
| Size | 27.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d870f20d1d8a024d8bfb1983de46d5f23d2913d9ec6081baa55b9206ef47dda
|
|
BLAKE2b-256 checksum How to use checksums |
9c3c319e1a4a34987959b5ac7be43dd0506f9e898f4a3118720d7b6c3871aa0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / altar_cherimoya-0.3.0-py3-none-any.whl
| Download URL | altar_cherimoya-0.3.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34f019b8c4c26119b0363d05c8ff070e8e99c714243c9098163d0b990b00cdc2
|
|
BLAKE2b-256 checksum How to use checksums |
d38877d6d117783ea08cb991b2c4e1315be21aef57fefe6e66db7e7be27c5836
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for altar-cherimoya 0.3.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.