Zelia local AI model repository
This repository is the public model distribution source for
Zelia — Organize your memories. Production inference is local and uses Windows ML.
No personal photos, thumbnails, embeddings, OCR text, face data, prompts, credentials or signing
keys belong in this repository.
Current validated stack
photo-organizer-stack/zelia-local-ai-stack-v1/
1licenses/
2ocr/pp-ocrv6/
3people/sface/
4people/yunet/
5vision/siglip2/
6manifest.json
| Capability | Asset | State |
|---|
| Visual similarity and classification | SigLIP2 FP16 DirectML | Validated |
| Correctness-first CPU fallback | SigLIP2 FP32 CPU | Validated |
| Text detection and recognition | PP-OCRv6 medium detection + recognition | Validated |
| Face detection candidate | YuNet | Stored; P10 product validation pending |
| Face embedding candidate | SFace | Stored; P10 product validation pending |
The rejected SigLIP2 INT8 experiment is intentionally absent from the current stack. Older dated
paths remain available through immutable Git history but are not the active organization contract.
Planned stack additions
- P09 benchmarks Qwen3.5-2B against Qwen3-VL-2B through ONNX Runtime GenAI and Windows ML. Only the
selected, reproducible ONNX package will be promoted here.
- P09 may add a small versioned offline place dataset alongside the model stack after its source and
attribution contract are approved.
- P10 validates the face detector and embedding package before Zelia can use the stored candidates.
- USearch/HNSW is application code, not a model asset, and is added only if the large-library
benchmark justifies it.
Integrity and releases
Zelia follows the approved Aurora-compatible trust level: HTTPS, immutable Hugging Face revisions,
exact byte sizes and SHA-256 hashes. No detached signing-key workflow is required. A stable channel
pins an immutable repository revision and exact manifest hash; the manifest then pins every asset's
path, size, SHA-256, provider contract, upstream revision, license and notice.
Published stack directories are immutable. A changed model, quantization, prompt contract or
runtime requirement receives a new descriptive stack version; dates are not version names.
