Altar ChromBPNet binding

altar-chrombpnet is the lightweight control-plane binding between Altar and the independently locked ChromBPNet runtime under runtimes/chrombpnet. Installing it registers CHROMBPNET through Altar's standard model-plugin entry point; the base altar distribution does not contain ChromBPNet-specific science.

pip install altar-chrombpnet

from altar.models import get_model_plugin
from altar_chrombpnet import ChromBPNetConfiguration

plugin = get_model_plugin("CHROMBPNET")

The binding owns ChromBPNet configuration, score schemas, prioritization, preprocessing, scoring, and interpretation plans. It depends only on Altar's public façades and Pydantic. TensorFlow, model code, weights, reference genomes, peaks, and provider SDKs remain outside the binding.

The binding also owns ChromBPNet's logical paths (altar_chrombpnet.layouts): the derived per-fold peak distributions and interval index, the staged peaks and motif set, and the interpretation run tree. Altar core provides only the model-neutral ModelArtifactLayout and ScoringLayout; every model-owned ChromBPNet file is composed from model_resource_file, so preparation and scoring name the same files under one layout. Staged file names come from the declared weights_format and peaks_compression, never from a resource URI.

Preprocessing can emit a manifest that records the ordered weights, peaks, genome, strand policy, producer image, and output digests. That provenance is additive: the normal scoring plan consumes the conventional peak-distribution and safe interval-index paths directly and does not require a manifest, an Altar-owned directory, or an adoption step. Standalone runtime callers may supply both --preprocessing-manifest and --preprocessing-identity to opt into strict verification. Historical scores and externally managed artifacts are not rewritten or recomputed.

Existing callers migrating from Altar core must install this package and replace imports such as from altar.models import ChromBPNetPlugin with from altar_chrombpnet import ChromBPNetPlugin. Registry-based callers need only install the package; the CHROMBPNET key is unchanged.