Maintainer workflows

This section collects repository and release material that ordinary prediction users do not need.

Contributing and verification

• Read the contribution guide before opening a pull request.

• Use Testing for the fast local loop and full verification commands.

• Use Development for internal API and compatibility-shim conventions.

• Use Orchestrator architecture when changing worker processes, hardware planning, or training data residency.

Training and model releases

Maintained operational documentation lives next to the scripts it describes:

• Training pipeline

• Release, synchronization, and deployment

• Generated model and data bundles

The public release entry point is:

mhcflurry train pan-allele-release --help

It coordinates training, evaluation, plots, remote artifact synchronization, and optional deployment. Deployment is never enabled by default.

Historical material

The 2023 retraining notebook audit is retained as a maintainer record, not as a current workflow. Use Evaluating trained models and the release guide above for current commands and artifact contracts.