Glossary

Admitted, held, rejected. The three verdicts. Admitted: the gate found nothing it could not settle, for that exact revision. Held: the gate found something that needs a person, for example thin licence evidence, and the model is not admitted until that is settled. Rejected: the gate found an automatic failure, for example the files are not in a safe format. See reading a verdict.

Attestation. A signed statement that a model passed the gate at a named version. It is minted only for an admitted model. Your policy names the attestation version for each model, and the enforcement hook requires the two to match.

Chain. The ledger's rows are linked so that changing or removing one breaks every row after it. See ledger and audit.

Compare. Running your own tasks across models and scoring the results with scorers you define. See Compare.

Declared. Stated by a person or an input file, not observed by Heliast. The evidence documents label what is declared and what was recorded.

Enforcement hook. The part of Heliast that decides whether each request may reach a model and writes the ledger row before the answer. It sits beside the gateway you already run, or behind Heliast's own router. Heliast is not a gateway. Other pages call it the hook.

Entitlement. A statement in your policy that a group may use a model. See policy and entitlement.

Environment. Anywhere a model runs: your own hardware, your private cloud, or an enabled hosted provider. See environments.

Evidence tier. How good the evidence for a licence is. T1 is the licence file in the publisher's repository, T2 is a full licence section in the model card, and T3 is a metadata tag alone. T3 is not enough to admit a model.

Footprint. How much memory a model's smallest published weights need: one card (24GB or less), one server (up to 128GB), or cluster (more). A property of the model, not of your estate.

Gate. The admission checks that produce a verdict.

Golden set. The tasks and expected results you give Compare to score models against.

Host record. The gate's verdict on one execution environment serving one model. A hosted route is never labelled verified, because weights on someone else's server cannot be checked. See environments.

Ledger. The tamper-evident record of every request: who, which model, the decision, token counts and prompt and answer hashes. It never holds prompt or answer text.

Policy. Your rules for who may use which model, and the limits and budgets on it.

Revision. The exact version of a model's files the gate assessed. A new revision is a new model to the gate.

Tier. A hardware size, Tier 0 to Tier 3, with pooled-memory hardware above them. See hardware.

Virtual key. A credential your people or services use to call models through Heliast. It belongs to a subject, carries groups and a role, and can be revoked.

Weights digest. A fingerprint of the model files. The pull tool refuses any file that does not match.