llama-seeds

Zeraix prefix-cache seeds and auxiliary assets

This repository holds assets consumed by the Zeraix desktop application. It is not a single standalone chat model: cache archives and auxiliary drafter files have different roles and compatibility requirements.

What is here?

• Prefix-cache seeds: precomputed KV state for the application's initial prompt and tool declarations. A matching seed can avoid recomputing that prefix on the first request.
• Auxiliary drafters: files under the drafters/ directory for specific speculative-decoding integrations. A drafter is not a replacement for its target model.

Compatibility matters

A seed must match the prompt/tool-prefix hash, pinned model revision, KV disk-format version, KV quantization, and the runtime's model/cache identity. The application selects compatible assets; do not mix archives across model or runtime versions.

The currently documented prefix-seed integration is macOS-specific. Its presence here does not imply equivalent Windows support. If a seed is unavailable or cannot be installed, the application is designed to fall back to a cold prefill.

See the public seed installer and identity rules and model configuration for exact version selection and drafter pairing.

Use through Zeraix

Download Zeraix and let the application manage these downloads. Generic Hub-generated model-loading commands do not describe how to load this mixed asset repository correctly.

Existing repository names, revisions, and paths are retained for application compatibility. This documentation update does not replace any cache archive or model file.

Related projects

• Runtime and sandbox assets
• Zeraix source and documentation
• Imparo inference engine, a separate project with its own state system and validation scope.

Licenses and provenance

Model-derived assets and auxiliary weights retain the applicable upstream model and component terms. This repository-level description does not relicense those files. Consult the model configuration, pinned source revisions, and relevant upstream model cards before redistributing an artifact.

For compatibility or provenance questions, open a Zeraix issue with the exact asset path and application version.