Admit a local artifact through explicit source, license, path, size, byte-count, hash, and structural checks.
Host intake record
Record source identity, license review, display name, expected byte count, SHA-256, trusted-root strategy, maximum size, reviewer, and approval state before model loading.
Canonical path and root
Resolve the candidate path, require containment under the trusted root, reject reparse points when the policy requires it, and avoid exposing the path in public evidence.
Identity before parse
Compare stable length and SHA-256 before parsing. Treat a mismatch as a hard failure; do not retry with weaker checks.
Structure after identity
Run bounded GGUF validation after identity verification. A structurally valid container can still fail architecture, tokenizer, tensor-storage, kernel, memory, or application checks.
Available now
- The public UAIX.LmRuntime package family and canonical package documentation.
- The host-facing workflow and evidence distinctions described on this page.
Host responsibilities
- Select and trust inputs, define policy and limits, integrate the UI or service, retain application evidence, and test the exact deployment.
Not claimed
- A digest is not a license or provenance result.
- The runtime does not acquire or approve models.
Operational boundary
What this page covers: Admit a local artifact through explicit source, license, path, size, byte-count, hash, and structural checks.
Available now: The documented package surfaces and this host-facing guidance are public.
Host responsibility: Own acquisition, trust, configuration, presentation, persistence, transport, policy, tests, and deployment.
Not claimed: Universal compatibility, production certification, safety certification, hidden fallbacks, or behavior beyond retained evidence.
Canonical sources: Canonical package documentation · Current release metadata
Last reviewed UTC:
Source and review record
Prerequisites
- Read Get Started
- Review host/runtime boundaries