claude
ab3e818bb9
querySources splits in two once you look at which sources over-claimed during the week of 2026-08-07. The clean ones perform a lookup and can come back empty: fact-by-key, tasks, list, money, calendar, notes. The dirty ones decide by cosine against frozen seeds and then answer whatever they claimed, because they have no lookup that could miss. Weather has no local table at all, which is why "что такое TCP?" became "для какого города?". So each source now carries its destination and whether it guesses, and queryWalk takes the guessers that were not named OUT of the chain. It removes and never reorders, which is the whole safety argument: the table's order is load-bearing, every comment on it argues a reason between two sources, and above all it carries "his data first, then the world". Naming SourceWorld does not send the turn outside. It stops weather claiming a protocol on the way past. His notes, his facts and the boundary in front of them still run first, so a wrong destination costs nothing but the guess it prevented. The skipped sources are recorded as never-asked with the reason, so /trace shows a narrowed walk rather than a chain that silently shrank. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>