A page that said “every” when it meant nine out of twenty-three

VEILOS publishes a page listing the guards that protect what you can and cannot see, and re-runs each one live as the page loads — checking both that it catches something it should hide and that it lets through something it should not. That page described itself as an account of every such guard VEILOS keeps, and said all ten were holding. Ten was simply how many were written on the list. A companion page on the same site works out, from the code itself, how many of these guards actually exist: twenty-three. So the page was describing itself as complete while covering nine of them. It now says nine of twenty-three, names the other fourteen outright, and the sentence you read is calculated from those numbers rather than typed beside them, so it cannot say “every” again until it is true. What this does not mean is that the other fourteen were unprotected. They are all proven live on the neighbouring page, and most already prove both halves there — the missing thing was the proof appearing here, not the protection. We have written the gap down as work rather than quietly widening the claim to cover it. Each guard also used to name the piece of code it protects in an ordinary sentence, which nothing could check; rename that code and the page would have kept citing a name that no longer existed. Those names are now real references, so a rename breaks loudly instead of silently. Separately, an internal tool we rely on to spot an unfinished release was found to be wrong about roughly half of this project's history — it was treating the paperwork each release files at the end as evidence that the release had never finished. Measured across the last four hundred changes: seventy-six of ninety-one completed releases would have been reported as unfinished, and forty-two of those reports would have been wholly wrong. It has been rebuilt to check the record itself rather than the wording of a filename, and it still reports a genuinely unfinished release.