Verify extraction provenance and prune semantic staging before inference
This commit is contained in:
1 parent
5c18e7b49c
commit
423a1ea57d
17 files changed
+900
-78
No files matched your search
@@ -77,11 +77,12 @@ 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
|
||||
cargo test -p searchi-service --test publication_google_cpu --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
|
||||
citations. Verify exact parser-input provenance and reject stale extraction before
|
||||
encoding; legacy records require a normal rescan. 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
|
||||
|
||||
Reference in new issue
Block a user