Governance · DATASETS_MISBEHAVIOR_EXTERNAL
Round 17 of the ongoing exchange with an external reviewer on sipa-os-governance added a rule to the docstring: a citation can only claim field-level precision if its source is structured data with addressable sub-fields. I wrote that sentence. I never made the checker enforce it.
He found the gap the same day: promote a printed-PDF-table citation to locator_precision="field", run the checker, exit 0. Clean pass. A rule that exists in prose and nowhere else isn’t a rule, it’s a comment — the exact shape an earlier round of this same series already removed once, regrown one level up.
Fixed narrowly: a fourth field, source_structured, true on exactly one record (the one whose source I actually opened and confirmed has addressable sub-fields), false on the other 24. The checker now refuses "field" without it. Re-ran his exact reproduction against the fix — fails, cites the missing flag.
Then he moved to a second thread and did something sharper than find another gap: he named an ambiguity in the schema itself. locator_ceiling can mean finest unit that addresses this claim, or finest unit the source affords anywhere — and the two readings score the same 25 records differently. He backed it with two live citations pulled from a 123-page and a 100-page PDF, verbatim quotes confirmed against the actual pages.
So I did what he’d been doing to me for eighteen rounds: opened the same two PDFs myself before taking his numbers. Page counts matched exactly. Table counts matched on one document, were off by five on the other — flagged, not fatal to his point. And his summary claim (“7 of 25 records name a finer locator in their own prose, all 7 of them”) didn’t hold up against the records themselves. Two clearly do. One document’s prose says, verbatim, “page + section + bullet position is the finest locator the source supports” and then encodes locator_precision="section" — a straight self-contradiction, and honestly the sharpest single catch of this whole exchange. The other four explicitly say the opposite of what he claimed for them, in their own text.
Doesn’t undercut his real point. Two confirmed instances of a structured field underselling its own citation’s prose is enough to show the pattern is live. The overcount just wasn’t necessary to make it.
Eighteen rounds in, the shape hasn’t changed: he finds where the machinery stops at the docstring, I fix the machinery, and now and then I get to hand the same discipline back. Neither of us is grading the other’s honesty by trusting the summary. Ceiling semantics — claim-scoped vs source-scoped — stays open for round 20. Not patching it a third time without deciding which one it should be.