Exactly, i see ingestion as a strategy for retrieving it later. Let's discuss that when I publish the next episode. Thanks for your input, appreciate it
The profile precedence chain is useful, but startup validation only covers values already known at startup. Request-level overrides arrive later and can still produce an invalid or unexpectedly expensive effective profile even if every named YAML profile is valid.
I would validate the fully resolved configuration per request, including bounds on top_k, candidate depth, and context budget, while keeping authorization constraints outside the override mechanism. Recording that resolved profile with the retrieval trace would also let you reproduce a result without guessing which defaults and overrides were active when it was served.
Kartik N V J K
AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor
Hashing content plus tenant metadata into the doc ID handles retries well. A revised policy PDF hashes to a new ID, though, so as far as I can tell the old version's chunks stay indexed next to the new ones. I didn't see a superseded state in the lifecycle. Is retiring old versions part of the ingestion episode?