Repository navigation
Migrate boltz2 to the semantic Task SDK #1434
Description
Parent epic: #1430
Status: Not started — comment here before beginning work.
Family: families/boltz2/
Current declared task mode(s): structure_prediction
Target semantic Task(s): Identify the existing semantic Task contract(s) that preserve every current capability; record the exact IDs in the PR.
Work
- Inventory this family's primary and secondary behavior, including batch, streaming, raw outputs and stateful operations where supported. Record the current defaults, profiles, checkpoint cases, and reference criteria.
- Implement and bind the matching semantic Task interface(s) in this family's runtime. Preserve its graph, preprocessing, inference, postprocessing, configuration and complete owned results.
- Align family-owned support, build metadata and manifests with the primary Task. Advertise only interfaces implemented by the loaded bundle; document whether existing bundles need rebuilding.
- Add family-owned CPU contracts and public C/C++ SDK consumers. Cover invalid inputs, configuration handling, result lifetime and every relevant lifecycle.
- Run a selected real checkpoint E2E with the existing oracle and thresholds, then check the remaining declared capabilities and public CLI, example and benchmark paths. Preserve meaningful passing criteria.
PR evidence
Link the migration PR here. Report the tested revision, exact commands and results, selected checkpoint cases, original reference checks, current-head CI, and any untested configurations. Keep a normal migration within families/boltz2/**; raise a separate linked prerequisite issue if a shared contract is genuinely missing. Do not weaken an acceptance criterion to pass CI.
References: #1226 · family validation guide.
Metadata
Metadata
Assignees
Labels
No labels
Activity
roma5087 commentedon Sep 29, 2026
Hi, I'd like to take the
boltz2migration.families/boltz2/on currentmainalready hasBoltz2PipelineimplementingIStructurePrediction, andplugin.cpp,support.pyandmodel.pyall usestructure_prediction. So I plan to do the following, modeled on the mergedmigration in #1308:
bindrecord /IModelbinding, if it isn't alreadycovered. I'll confirm this against the current runtime first.
validation, complete result ownership (samples, confidence, metadata) and
unsupported config.
the result after releasing the model and must agree on the structure output
and confidence values.
README.
and thresholds. I'll report the exact revision, commands, results, and
anything I couldn't test.
I'll keep all changes inside
families/boltz2/**. I'll open a separateprerequisite issue if I find a shared contract is missing, and I won't weaken
any existing acceptance criterion. I'll link a single migration PR here.
yifeif-nv commentedon Sep 30, 2026
Sounds good. Please go ahead and start a PR and link it to this issue!