File: backend/app/cache_manager.py:108-110
The number/year guard requires the incoming and cached query's numeric-token sets to match exactly, rather than checking whether the differing number is actually relevant to the cached answer.
Failure scenario: An incidental number difference not tied to the actual answer (e.g. an unrelated figure the user mentions) forces a cache miss even when the queries are truly equivalent. Minor compared to the other findings; not a correctness/safety bug, but shows the fix is a blunt set-equality check.
See docs/rag-audit-findings.md (item 7).
File:
backend/app/cache_manager.py:108-110The number/year guard requires the incoming and cached query's numeric-token sets to match exactly, rather than checking whether the differing number is actually relevant to the cached answer.
Failure scenario: An incidental number difference not tied to the actual answer (e.g. an unrelated figure the user mentions) forces a cache miss even when the queries are truly equivalent. Minor compared to the other findings; not a correctness/safety bug, but shows the fix is a blunt set-equality check.
See
docs/rag-audit-findings.md(item 7).