tri census audit: every census, counted twice

Four census populations recounted another way all agree; three are named as uncheckable.

t27 · tri census audit

  census's own reader would agree by construction.                                                      

      census                   printed  counted here   population                                       
      unparsed report             1269          1269   .t27 files                                       
      quantifiers report           888           888   lines carrying a quantifier keyword              
      mods orphan                  155           155   .rs under every workspace member                 
      lean vacuous                 250           250   `theorem` lines in Completeness.lean             

  AGREED. Every census speaks about the population it prints.                                           

  Not checked here, and why -- because a page of green rows looks                                       
  like coverage until somebody asks what is missing from it:                                            

      seals hollow                                                                                      
          built and removed. Its counter tested json text for `"spec_path"`                             
          while the census parses that same field, so planting one more seal                            
          moved BOTH numbers to 1314 and the row stayed green. No input makes                           
          them disagree.                                                                                

      types dup                                                                                         
          measured: a counter loose enough to be independent reads 1182 where                           
          the census reads 1180, and the two extra are `struct = 21,` -- enum                           
          members named `struct`, which the census correctly rejects. Any                               
          counter accurate enough to agree is a copy of its matcher.                                    

      discard classify                                                                                  
          its population is parser events produced at run time, not artefacts                           
          on disk. Counting them a second way means running the same parser,                            
          which is not a second opinion.                                                                
t27 $

recorded 2026-10-03 16:18 UTCreal 14.9 sshown 4.9 sexit codes 0

$ tri census audit

Staged: the prompt and the typing. Real: every byte the commands printed, at the time they printed it. Any silence longer than 2 s is shown for 2 s, and the title bar says so while it happens. Edited: home directory shown as ~.

GIF Preview card