One signed binary. Every feature compiled in. Free to run. Install Crowkis →
← back to the Roost
featuresJune 28, 2026· 5 min read

One similarity cutoff is always wrong

'What's 2+2?' needs a near-exact match to reuse safely. 'Give me creative ideas for X' can tolerate a loose one. A single global threshold guarantees you're too strict somewhere and too loose somewhere else.

Every semantic cache has to draw a line: how similar is similar enough to reuse an answer? The tempting move is to pick one number and apply it everywhere. It's also a guaranteed mistake. A factual lookup needs an almost-exact match before you dare reuse it. A brainstorming prompt can share an answer with a much looser cousin. One line can't serve both.

In plain words: Crowkis sets the reuse threshold by the kind of question. Factual questions demand a tight match; open-ended ones allow a looser one, and the thresholds adjust over time from real feedback.
how strict a match should be, by intent
factual lookup ('what's the refund window?')96 · very strict
comparison / how-to86
recommendation80
creative / open-ended72 · looser

The bar for reuse moves with the question, strict where correctness is binary, relaxed where it isn't.

And it isn't static. When users correct an answer or regenerate one, that's a signal the threshold for that kind of question was too loose, and it tightens. The cache tunes its own caution per category instead of forcing you to pick one compromise that's wrong everywhere.

The bottom line

Similarity isn't one bar; it's many. Match the strictness to the stakes of the question, and you stop trading correctness for hit rate, or hit rate for correctness.