How the gate decides
One named, versioned artefact per model, so the answer to "can we use this?" is a document rather than a conversation.
What the artefact carries
Every candidate gets one artefact, versioned against the gate run that produced it: the document you read before a model goes near your workloads.
- Licence and evidence path
- The licence identifier from the licensor's own repository metadata, with the source named rather than assumed.
- Canonical-text pin
- The canonical licence text pinned by SHA-256 on an allow-listed source, and digest-verified against that pin on every run.
- Added-clause screen
- The added-clause screen run over sibling policy files (usage policies, notices, gated prompts), so a clause outside the licence file surfaces as a hold, not a surprise.
- Provenance chain
- The licensor repository, whether it is the licensor's own, and any derivation or base-model note, so the chain from weights to publisher is recorded.
- Export screen
- Who assessed export control, on what basis and with what result: not yet assessed, so the artefact says so and no export claim is made.
- Hardware fit
- Which accelerators it has been seen to fit, and at what precision, so sizing starts from evidence.
- Indemnity position and attestation version
- Where the indemnity question stands, and the admission attestation version the artefact is bound to.
- Status
- Admitted, held or rejected, with the violation list attached whenever the answer is not admitted.
Admitted, held or rejected
Admitted
The gate passed. The model enters the catalogue with its artefact attached, and an entitlement can resolve against it at a named attestation version.
Held
Something is missing or undecided, such as no licence file or an added policy still being classified. Recorded with its reasons; not admitted.
Rejected
The answer is no: a declined licence class or a clause the gate will not admit. Recorded the same way, and never admitted.
Reading a verdict
- One revision. A verdict covers the exact revision assessed; a new revision gets its own.
- Licence, provenance and files. Quality and fit on your own tasks are measured by Compare.
- Evidence for your reviewers. The record is built to hand to your legal, risk and compliance teams.
- Labelled provenance. Weights we byte-checked are labelled verified; hosted routes are in build, and one would be labelled provenance by host attestation, not verified.
- Export. Export screening is not yet assessed, and no export claim is made.
- Backfill. The first verdicts were assessed before release tracking began, so they show no release-to-verdict time.
Why this is what we sell
Every platform team asks this about every model that lands, and again each time a release or licence changes. We adjudicate once and every estate inherits the answer.
Deciding which models your teams may run? Heliast runs this gate inside your environment, on your policy, for every model you use.
Book a discovery session