Skip to content

Epic: Migrate remaining model families to the semantic Task SDK #1430

Open
0 of 2 issues completed
Open

Description

@yifeif-nv

Goal

Migrate each remaining model family to the semantic Task SDK introduced in #1226. Each child issue covers one family so contributors can implement and review migrations independently.

This inventory is based on public main and open PRs checked on 2026-09-28: 112 families remain, including 21 covered by open Task migration PRs and 91 not started. Families already using semantic Task bindings are excluded.

Contribution boundary

  • Keep a normal migration within families/<family>/**. Preserve every existing primary and secondary capability, including batch, streaming, raw-output and stateful paths where applicable.
  • Map each capability to an existing semantic Task contract; bind only Tasks implemented by the loaded bundle. Keep model-specific preprocessing, inference, postprocessing, configuration and tests with the family.
  • Preserve existing checkpoint cases, numerical oracles, thresholds, supported profiles, and CLI, example and benchmark behavior. Do not weaken passing criteria to pass CI.
  • Add public C and C++ SDK coverage and report actual build/load/run and reference evidence. State untested configurations honestly. Rebuild bundles when the primary Task changes.
  • If a family exposes a genuinely missing shared contract, open and link a separate prerequisite issue before completing that family. Do not add a shared model implementation or a cross-family dependency.

Coordination

Comment on a Not started child issue before beginning work. One family should have one migration PR linked to its child issue. An open PR already covering a family is marked In progress and is not available to claim. Separate family CLI work is linked for coordination but does not count as Task migration progress.

The child-issue checklist below is the source of truth. Close this epic when every child issue is completed or publicly resolved with an explanation.

Child issues

Native sub-issue groups: #1543 (families A–M, 54 issues) and #1544 (families N–Z, 58 issues). GitHub allows at most 100 direct sub-issues per parent, so the family issues sit one level below these two groups. The checklist also links every family directly for status tracking.

In progress (21)

Not started (91)

Public references

Metadata

Metadata

Assignees

No one assigned

    Labels

    CommunityCommunity related issues

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions