Computational chemistry campaigns span workstations and institutional clusters, while calculation software changes during development. We present vibe-queue 1.0.0, an open-source execution layer connecting inputs, resource requests, runtime identity, execution state, and recovered outputs. Background services run local and SSH-accessible jobs; external drivers submit cluster jobs through Torque/PBS or Slurm. Fixed runtime environments preserve selected software across updates. Portable bundles, recorded resource estimates, host-selection policies, and a fleet dashboard support distributed campaigns. An authenticated HTTPS gateway accepts submissions without fleet network access, while linked workflows connect calculation, validation, and rendering through checksummed transfers. Existing programs execute as separate processes, including vibe-qc; retrieved results can be inspected with vibe-view. We describe the architecture, operational limits, and chemistry workflow for the fixed 1.0.0 release. Its release-candidate verification record contains 13,149 passing tests and 37 skipped tests. These checks support documented software behavior; scientific correctness and suitability for a particular cluster require separate validation.
No takes yet. Share an insight, caveat, or question.
Michael F. Peintinger (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: