HPC deployment

The current-runtime candidates are in packaging/current/. They require Python 3.15.1 and mirror the canonical core policy. They are not published releases or verified HPC installations. Source qualification, dependency solving, native builds and installed-module probes remain separate gates.

Build preparation

Inspect packaging/current/runtime.json and run the declaration validator with the repository interpreter through the resource guard:

.venv/bin/python scripts/guard_verification.py \
  --work-dir .conductor/local/current-overlay-check \
  -- .venv/bin/python scripts/check_current_overlays.py

The Spack development recipe binds an immutable migrated source candidate. The EasyBuild candidate requires a source archive and hash qualified against that source identity before activation; it cannot fall back to a published older source or download missing dependencies silently. See packaging/current/README.md. No catalogue availability, solver result or native build is inferred from these declaration checks.

Cluster modules

Keep each compiler/toolchain’s modules separate. Qualify the source archive, Python runtime, native extension, numerical reference and Arrow round-trip on the actual cluster before claiming installed-module acceptance.

The older source-bound recipes, licences and evidence remain at their original paths and are hash-pinned by packaging/current/overlay-lifecycle.json. Their old runtime graphs and replay helpers are historical evidence, not current installation defaults. The pre-migration instructions are retained unchanged in docs/release/hpc-deployment-pre-315-20261028.mdx for audit only.