Inference Passports
An Inference Passport answers four release questions with persisted evidence: what revision ran, which immutable artifacts and runtime configuration it used, how it was measured, and which policy decision allowed it to ship. It is an evidence envelope, not a compliance certificate.Configure signing
Generate an Ed25519 key once on a trusted operator machine:0600 and refuses to overwrite an existing key.
Mount the key into the control-plane process. On platforms that inject secrets as environment
variables, set INFERCRANE_PASSPORT_SIGNING_KEY to the file’s contents instead; the container
entrypoint writes it to an owner-only file before the server starts. InferCrane persists only the
public key, key identity, signature, digest, and signed payload. Back up and rotate private keys
using your normal secret management system.
Issue and verify
- immutable revision ID and complete normalized
DeploymentSpec; - resolved model repository, immutable revision, model identity, and known cache state;
- runtime, runtime version, OCI workload identity, provider, region, GPU, and compute mode;
- revision-scoped AIPerf result identities, workloads, reproduction commands, and sourced cost data;
- available cold-start measurements and explicitly unavailable timing boundaries; and
- the latest relevant Release Guard policy, metrics, reasons, decision, and evidence identity.
verified but reports complete: false and deterministic
missing_evidence codes. GitHub release checks require both verified and complete; a signature
alone is never treated as release qualification.
PostgreSQL stores the canonical payload byte-for-byte rather than normalizing it as JSONB. This is
required so offline verification remains stable after reads, backups, and restores.