oz0 model vet
For: Operators and developers looking up a command.
A model behind a built-in provider or a shipped preset counts as vetted. A local model, and a model behind an endpoint with a base URL of the tenant's own, is unvetted until a tenant admin vets it: a job that may run on an unvetted model starts tainted, so each call that can send data out waits for a person, and it runs on a node with sandbox tier 1 only. It is never refused for its model.
A vetting is a person's judgement with a reason, not a scan of the weights, and never says a model is safe.
Vetting loosens what the model's jobs need: it takes a reason and, where the tenant has four eyes on, another admin's approval. A local model's vetting holds for the digest its nodes report now (they must agree; --digest names another), and ends while a node serves other weights under the name; when no node reports a digest, name one with --digest or vet it by name with --by-name, which covers any weights served under the name.
An endpoint's vetting holds while its provider record calls the base URL it calls when the vetting is asked for; an approval never applies it to another. The vetting is audited (provider.model_vetted) and goes into the evidence bundle.
Usage
oz0 model vet <provider>/<model> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--base | string | the model it was edited from (fine-tuned, merged or abliterated), for the record | |
--by-name | bool | vet a local model by its name alone, for any weights a node serves under it (only when no node reports a digest; the change and the audit show it) | |
--decision-ref | string | the decision or case the change follows, such as a case number (at most 200 characters) | |
--digest | string | a local model's sha256:<hex> to vet; default the one the tenant's nodes report | |
--json | bool | print JSON instead of a table | |
--publisher | string | who published the model, for the record | |
--reason | string | why, required for every governance change (at most 500 characters; default $OZ0_REASON); the audit log keeps it | |
--source | string | where it came from, such as a Hugging Face or registry reference, for the record | |
--tenant | string | default | tenant whose model it is |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.