Experimental tutorial · P6
Rerank retrieval,
one variable at a time.
p6_rerank_retrieval reuses a compatible P0 index and enables only the server-owned reranker.
P0 → P6Single-variable experiment
Server-owned rerank
What changes
Only rerank.
P6 keeps P0 retrieval and invokes the existing reranker after retrieval.
What is disabled
No hidden defaults.
Evaluator v5 removes pipeline, cache and routing, and keeps rewrite, HyDE and multi-query off.
What is inherited
The P0 index facts.
No duplicate indexing occurs. Durable audit fields record P0-index reuse and rerank state.
When comparison is valid
Only direct P0 → P6.
The API requires a compatible evaluator-v5 P0 parent, the same knowledge base and frozen evaluation inputs.
Reproduce it
Run the controlled walkthrough.
The real browser regression starts PostgreSQL, Qdrant, migrations, API, Console, and a controlled immutable Pack. It runs P0 then P6 and verifies rerank audit facts and P0-index reuse.
$ make console-real-tutorial-clone-e2e ✓ P0 baseline completed without rerank ✓ P6 enables rerank ✓ P0 index facts inherited ✓ direct P0 → P6 comparison ready