Expand description
Startup model verification (design decision §3, RFC-021).
Runs at every startup. Checks that the files required for the configured embedding model are present and non-empty. Does not run SHA-256 hash verification — that is reserved for the explicit “Validate” action in the Models view (keeps startup under 5 ms).
The two required files inside the model directory:
onnx/model.onnx— the weights (typically 20–140 MB)tokenizer.json— the tokenizer config (~2 MB)
Structs§
- File
Issue - A single file that failed the verification check.
- Model
Manifest - A manifest file written alongside downloaded model files. Contains the SHA-256 hash of each file at download time so the explicit “Validate” action can detect corruption or tampering.
Enums§
- Deep
Verify Outcome - Result of a deep (checksum) verification.
- File
Issue Kind - Reason a required model file failed verification.
- Verify
Outcome - Outcome of a startup model verification check.
Constants§
- REQUIRED_
MODEL_ FILES - Files that must be present in the model directory.
Functions§
- verify_
embedding_ model - Verify the embedding model directory at startup.
- verify_
embedding_ model_ deep - Run a deep integrity check using the stored manifest (RFC-029). Called only from the explicit “Validate” button in the Models view — never at startup (would add 50–500 ms for large models).
- verify_
outcome_ summary - Run the verifier and return a brief log-friendly summary string (never includes file contents — NFR-014).