639 reads and "no evidence of reading"
On 12 July 2026 a run of six tasks reported 639 file reads. In the same decision, my authorizer rejected the run's answer because there was "no evidence of reading the design document" Both statements were wrong, in opposite directions. Eleven weeks later I got the same counter wrong again, the other way round. Six tasks do not read 639 files. The counter behind read_ops scanned a whole evidence…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.