Finish the selection map, and price it honestly
The cache already declares and persists what type each member is, so numbers cost no migration. What they do cost is a public way to read a declared value at all, because the evaluator today cannot reach one from outside the cache, which is why the existing snapshot loop reflects. That is a hundred and fifty lines, not sixty, and the ledger moves the wrong way to say so. Three claims inherited from the earlier pass were wrong and were cut rather than designed around. A fifth selector engine turned up in Rust. And the cache's index maps keep one key per value, so an evaluator that reached for them would answer a query about a whole family with a single row. Watching a selection is mapped as its own cut, where nine overloads that are a query language in disguise collapse into one. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
parent
211b5e320f
commit
ee91062cee
1 changed files with 797 additions and 96 deletions
File diff suppressed because it is too large
Load diff
Loading…
Reference in a new issue