Reuse completed Google embeddings and resume semantic staging
This commit is contained in:
1 parent
0b56ab553c
commit
5c18e7b49c
11 files changed
+1677
-148
No files matched your search
@@ -73,6 +73,17 @@ SEARCHI_GEMMA_MODEL_DIR and SEARCHI_GEMMA_WORKER, then run:
|
||||
cargo test -p searchi-semantic --test gemma_cpu -- --ignored --nocapture
|
||||
```
|
||||
|
||||
Incremental reuse/recovery additionally requires verified CPU FFmpeg helpers in
|
||||
SEARCHI_TEST_FFMPEG and SEARCHI_TEST_FFPROBE. Run the actual Google integration:
|
||||
|
||||
```sh
|
||||
cargo test -p searchi-service --test incremental_google_cpu --test google_cpu --locked -- --ignored --nocapture --test-threads=1
|
||||
```
|
||||
|
||||
Completed-group reuse must preserve actual vector bytes and remap current source
|
||||
citations. Do not substitute simulated vectors or treat zero encoder calls as a
|
||||
foreground latency benchmark. See docs/INCREMENTAL-SEMANTIC.md for remaining gates.
|
||||
|
||||
Record actual outputs, hardware, corpus size, background preparation, first-input
|
||||
latency and warm latency in the relevant validation report. Unexecuted platform
|
||||
checks stay open. Compilation alone is not UI interaction verification.
|
||||
|
||||
Reference in new issue
Block a user