"_comment":"Relative-ratio regression gates (the maintainer's chosen policy). Ratios are portable across machines/WAN; absolute ms in the results JSON stay informational. Tune these after the first real baseline run, then tighten. 'field' is a dotted path into a metric's result; for list items use the index (e.g. sweep.3.median_ms).",
"why":"concurrent read_many must beat serial by the 1.1.0 concurrency margin; <1.8 means concurrency regressed"}
]
},
"bulk-get":{
"gates":[
{"field":"speedup_ratio","op":">=","min":1.5,
"why":"controlled-K concurrent vs serial; lower bar than full-vault since K is small"}
]
},
"expand-graph":{
"gates":[
{"field":"min_speedup","op":">=","min":2.0,
"why":"recall()'s graph layer must fetch each BFS hop concurrently (read_many), not serially per node; <2x means expand_graph regressed to the pre-fix serial walk"},
"why":"cold request must be meaningfully slower than warm — proves keep-alive is reusing the connection; a ratio near 1.0 means every request is re-handshaking (the pre-1.1.0 bug)"}