Repository navigation
nullius v0.8.0
Two broken agents, an eval record that read a failure as green, and a third less prose.
The prose
invariants/*.md: 1,933 -> 1,158 words. Every rule survives -- the bold rules were
diffed before and after, 39 in and 39 out, and the one genuine loss, a reviewer-proof
paper does not exist, was restored. What went is the argument around each rule, which
WHY.mdandalgorithms/already carry. All four tables stay: they are the vocabulary,
not prose.voice.mdlost most (560 -> 262) and had been injecting a reference toprose,
a command deleted two hours earlier. SessionStart on an empty project: 2,569 -> 1,794
words, below where the day started.- README: 4,841 -> 2,542 words, twenty minutes to eleven. Twelve sections argued for one
mechanism each. They are one table of what refuses and one paragraph of what reports; the
arguments were already inWHY.mdandalgorithms/. - CHANGELOG: two entries at 1,413 and 811 words against a historical median near 430. A
changelog says what changed and why it was wrong before; those re-argued the design. paragraphs()treated a figure's alt text as prose. The 82-word alt text atop this
README counted as its opening paragraph, socheckcalled the file no short version at
the top when its first sentence is thirty words. It also inflated the cross-file
duplication count used to argue for this cut: 34 pairs measured, 11 real. The headline
number was partly an artifact of the instrument that produced it.- Also cut:
WHY.mdsection 12, which was credentials and a build order; section 5's
table, which iswarrant.md's;algorithms/README.md's prose, which wasCONTRIBUTING's;
examples/README.md's account of files that no longer exist; and
evals/results/06-2026-09-02.md, which held two runs concatenated with a failure first.
Repository prose: 43,974 -> 39,341 words.
The machinery
A second pair of clean-context reviews, one on the prose and one on everything that is not
bin/nullius. The prose one measured what the tool's own repetition detector found when
pointed at the repository for the first time: 34 cross-file paragraph pairs sharing half
their content words or more, and a README that check reads as 4,568 words, twenty minutes,
no short version at the top.
agents/referee.mdmandatedmajor-revisionandminor-revision.DEFAULT_SCALEis
desk-reject / major / minor / accept, so an agent obeying its own file was refused by
nullius verdicton every review. It now names the venue file's scale, which the same file
said two paragraphs earlier.agents/librarian.mdhad thescreenarguments in the wrong order, documenting
screen <search> <index> <include|exclude>where the index is a flag. An agent following it
failed on every screening call.- The eval runner never truncated its output file.
tee -ainto a name keyed on the date
means a same-day re-run concatenates, andresults/06-2026-09-02.mdis two runs in one
file: the first ends| 8 | 1 | 0 |with a gate that should have refused and did not, the
second ends| 9 | 0 | 0 |. A reader taking the last table read a failed run as green. - The bytecode check added this morning reported an untruth. It said tracked and
globbed the working tree, so an untracked, gitignored.pycturned preflight red on a
clean repository. That is the5 passed, 1 failedseen earlier today and waved away as
transient. It was not transient. It readsgit ls-filesnow. - Three byte-identical venue skeletons, and two duplicate eval results. The three
examples/*/venues/EXAMPLE.mdhad the same md5 as each other and astemplates/venue.md,
whichinitalready writes, so copying a worked field into a project overwrote a copy of
itself.results/04-and05-2026-09-10.mddiffered from their 09-02 twins by a timestamp
and one citation count. examples/README.mdclaimed index presetsinitdoes not pick. True for
clinical-ml, false for the other two:FIELD_INDEXEShas no key matching language
models or social science.- About 900 words of restated argument. WHY.md section 6 was
invariants/status.mdwith
the column headers reworded, and section 7's boundary subsection was the third telling of
whatalgorithms/critique.mdcarries with its parse schema. The injected files are
canonical because they are the copy a session actually sees. The duplication was not only
bloat: today's correction to the folklore claim reached two of the four places it was
stated, and section 6 was still describing a citation walk that does not exist. - The README's
Where the rest of it issection opened by saying nothing is summarised
back here and then summarised five files for thirty-five lines.
A finding checked and rejected. The machinery review reported that PostCompact is not a
Claude Code hook event and that the entry in hooks/hooks.json is inert. It is a valid event,
per the official documentation, and it fires. The constraint re-injection that
REFERENCES.md cites chen2026 for does happen. Acting on that finding
unchecked would have deleted a working mechanism, which is the whole argument for checking.