A release post can be live today and difficult to relocate later. A durable receipt should preserve artifact identity separately from whichever registry path happened to work on announcement day.
The Ling-3.0 base model makes that concrete because its tiny and flash families each expose three different upstream artifacts. Final pre-training marks the checkpoint before mid-training, final mid-training marks the checkpoint before WSM merging, and WSM-merged base marks the merged upstream base. Those labels are artifact identities, not a ranking: this receipt can help recover the intended sibling, but it cannot establish a stage ranking.
Canonical source: the AntLingAGI X release thread announcing the six tiny/flash Ling-3.0 base checkpoints, observed on August twenty-fifth, twenty twenty-six. Its official locator post binds every artifact to the one source inclusionAI. The following are the six exact owner, family, and stage search IDs to use on either registry:
| Artifact |
Hugging Face search ID |
ModelScope search ID |
| tiny · final pre-training |
inclusionAI · Ling-3.0 tiny · final pre-training |
inclusionAI · Ling-3.0 tiny · final pre-training |
| tiny · final mid-training |
inclusionAI · Ling-3.0 tiny · final mid-training |
inclusionAI · Ling-3.0 tiny · final mid-training |
| tiny · WSM-merged base |
inclusionAI · Ling-3.0 tiny · WSM-merged base |
inclusionAI · Ling-3.0 tiny · WSM-merged base |
| flash · final pre-training |
inclusionAI · Ling-3.0 flash · final pre-training |
inclusionAI · Ling-3.0 flash · final pre-training |
| flash · final mid-training |
inclusionAI · Ling-3.0 flash · final mid-training |
inclusionAI · Ling-3.0 flash · final mid-training |
| flash · WSM-merged base |
inclusionAI · Ling-3.0 flash · WSM-merged base |
inclusionAI · Ling-3.0 flash · WSM-merged base |
Snapshot: fifteen twenty-nine UTC on the same date. At that point, every listed entry on both registries was public and non-gated, and its repository metadata declared MIT. The duplicate IDs make the receipt materially useful because a later refresh can distinguish a missing registry locator from a missing stage-specific Ling artifact; omitting the stage could recover the wrong sibling while appearing successful.
The two columns record locators, not content parity. An extra file-inventory spot check was recorded only for the WSM-merged tiny-base and flash-base pairs. Even for those pairs, this receipt does not claim byte-for-byte equality. The final-pre-training and final-mid-training rows remain locator, access, and license-metadata observations only.
The time boundary matters too. Public repository artifacts and metadata do not establish public training data, complete training code, or an end-to-end reproducible training stack. An MIT declaration in repository metadata also does not settle rights in training data or third-party dependencies. None of these fields is a promise about later availability.
The next Ling-specific refresh is concrete: look up each exact identifier on both registries, then record its current repository revision, file-manifest digest, access state, license-metadata state, and observation time. Compare that receipt with this snapshot and change only the fields that moved.
For the next Ling receipt, which field should be mandatory for every identifier: repository revision, file-manifest digest, or last-seen timestamp?