POST /configure changes it until the next restart),
yaml is what comes back after a restart, default is what you get by saying nothing.
A row marked twiddled is a live change nobody wrote down;
set is a value the yaml chose on purpose.
The callosum reads only each store's rank ordering - never its raw scores - and fuses with
Reciprocal Rank Fusion: weight / (k + rank). Because it ignores magnitudes,
the merge survives any store swapping its embedder. Per-store weight is the only cross-store trust lever;
per-store floor guards against rank-1-of-garbage. A slow or down store is skipped for that call - it degrades the
result, it never takes the fan down.