COMPUTED MODEL · TRACE THE CAUSE

Which revision did the index publish?

Change chunking, reuse and the commit boundary. The visible index is rebuilt from actual selected words; a fingerprint mismatch identifies reused representation for different text.

v1visible source revision
0text/fingerprint mismatches
splitfirst policy condition

Try this

Use chunk size 4 and interrupt after one new chunk. Atomic publication keeps the complete old revision; incremental publication exposes a mixture. Finish the import with ordinal-only reuse: the new text can retain an old representation fingerprint.

Plain-word chunk and revision model, not PDF parsing, cryptographic provenance or embedding inference. Fingerprints are stable model labels for exact text. The condition check tests whether the known first policy sentence remains together. Real semantic quality, hash policy, storage transactions and model parity require separate evidence.