- Lesson 1: What is a System One model?
- Lesson 2: System One models and LLMs
- Lesson 3: How they decide
- Lesson 4: Your first API call
- Lesson 5: Pull a model
- Lesson 6: Run a model on your machine
- Lesson 7: Check, measure and calibrate with NoulXP
- Lesson 8: Fine-tune on your own data
- Lesson 9: Publish your model
LESSON 9 OF 9
Publish your model
Put your model on the registry with one command, with its model card, evaluation and lineage, and learn how a model earns the NoulXP compatible badge.
Before you publish
You need an account with a verified email address. Your username is your
namespace, so your models live at username/model-name. Browsing needs no
account; publishing does.
Sign the CLI in. It shows a code and opens your browser, where you check the code and approve:
systemone login
systemone whoami
Publish a folder
Point push at the folder that holds your model, and look before you send:
systemone push ./my-router --repo you/my-router --dry-run
systemone push ./my-router --repo you/my-router
push finds the weights (model.safetensors, model.onnx, a .gguf or
an .mlpackage) and writes the rest for you:
- The manifest,
systemone.yaml: what the model decides, its runtime, its base model, and its evaluation from the studio'seval.json. - The model card: the folder's
README.md, or one written from the evaluation. - The version:
0.1.0the first time, then the next minor version. A published version never changes.
--dry-run prints the manifest, the card and the files, and stops. Files the
registry already holds are not uploaded again. In System One Studio, the
Publish button does all of this in one click.
What you get
A page at /you/my-router with the model card, the files, the evaluation and
a link to the base model. Anyone can pull it with the command from lesson 5.
If the System One Engine can run its files, open the model's Playground tab and request a live playground. Once it is approved, the model answers there and through the inference API.
The NoulXP compatible badge
If your model has a NoulXP package, put it in an noulxp/ folder next to the
model, and check it before you publish:
noulxp validate noulxp/ # schemas, parsers, coverage, hashes
noulxp check noulxp/ # replays conformance.jsonl through the reference runtime
After you push, the System One Engine checks the package itself (packages up to 2.5 GB). When it passes, NoulXP compatible appears on the model's page and on your profile. The badge cannot be requested: it is earned only by publishing a model whose package passes.
Try it
Sign in from your terminal
systemone login systemone whoami
Look before you publish
Run
pushwith--dry-runon a model folder, such as a run from System One Studio. Replaceyouwith your username.systemone push ./my-router --repo you/my-router --dry-runPublish it
systemone push ./my-router --repo you/my-routerCheck a NoulXP package
Only if your model has one.
pip install "noulxp[onnx]" noulxp validate noulxp/ noulxp check noulxp/
Read more
Every lesson is open to read. Sign in to tick them off and claim the certificate at the end.