docs(release): crossLink — 1985 counts emitted relations, not CSV cells (unit label) - #948
Merged
Merged
Conversation
…ls (unit label)
The number was already right and already reconciled; only the unit word was wrong.
RELEASE-NOTES-v0.9.0.md said "1985 cellules across 844 fallacies", while CHANGELOG.md
said "1081 cells across 844 fallacies (59.9%)" for the same layer. A reader comparing the
two release documents sees a contradiction where there is none: 1985 counts emitted OWL
relations, 1081 counts non-empty CSV cells.
Measured on master before editing:
- 1081 non-empty crossLink_* cells in Cards/Fallacies/Argumentum Fallacies - Taxonomy.csv,
of which 137 are multi-valued (";") -> 1230 individual targets
- 844 rows carry at least one crossLink = 59.9% of 1408 (matches every doc)
- 1977 AnnotationProperty references to the 8 crossLink IRIs in docs/ontology/argumentum.owl
(exact IRI match; a naive grep on the bare verb also hits prose, e.g. "lighting and
mirrors in our store" at line 28587)
- 8 ObjectProperty declarations, one per verb -> 1977 + 8 = 1985
That last delta is NOT a new finding: docs/ontology/aif-export/README.md:73 already
documents it ("Raw parse = 1977 ~ README 1985, the -8 delta is one schema self-definition
counted per verb, 8 verbs"), and 1985 is the figure asserted by the passing test
LoadedOntology_ContainsCrossLinkAndAifAttackAssertions and used consistently across
docs/ontology/README.md, the #133 publication certificate and CHANGELOG.md:52. Nothing is
renumbered here.
498-reconciliation-p1-closure.md attached "(59.9% of leaves)" to 1985; the 59.9% belongs
to 844. Same fix.
Refs #763, #133
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jul 26, 2026
…e unreproducible numbers rectified (#950) The release dossier is the publication GATE (#134), so its byte-exact figures have to be reproducible by whoever verifies the tag. §3.4 had three that were not. Measured on master `accfeeab` (`git cat-file -s` on the committed blob): 1. Size. §3.4 printed 5,314,381 B. That matches NO committed blob: `c2a9b761` (its own reference) and `d206e59c` are both 5,378,765 B, master is 6,030,505 B. The gap to `c2a9b761` is exactly 64,384 B -- the "-64 KB" claimed in the same sentence, i.e. the delta looks subtracted twice. Corrected to 6,030,505 B, with the commit and the representation named (blob == worktree here; the blob already carries CRLF, so `core.autocrlf` creates no discrepancy). 2. Provenance. §3.4 credited the "régén fraîche" #634 / `c2a9b761`. That commit left NO change in `docs/ontology/`: `argumentum.owl` has the identical blob `3c76b691…` at `d206e59c` (March) and at `c2a9b761` (July), and `argumentum_virtues.owl` is absent from `c2a9b761` entirely although the section claims it was committed there. Both files come from #787 / `6fdf5726` (2026-07-12): +651,740 B, +9,733 lines, +1,977 crossLinks, +290 AIF assertions. Two readings remain possible from git alone (regen reproduced byte-identically, or its output was not committed) and the doc now says so rather than picking one -- the missing Virtues file leans toward the second. Either way the freshness the tag gate requires is satisfied by #787: the citation was wrong, not the conclusion. 3. Unit. "1 408 broader" is a raw grep count (identical at every commit, so reproducible as printed) but it counts 1,407 hierarchy edges plus the property declaration. 1,407 edges / 1,408 concepts -- the root has no parent. Same class of confusion just fixed in #948 for crossLinks (1,081 CSV cells / 1,977 assertions / 1,985 with declarations). Confirmed exact and left alone: 1,408 fallacies, 2,816 prefLabel, 5,558 EN literals, 862,709 B for the Virtues OWL. Flagged as mixed-provenance: the 4,861 FR count is post-#787 (it was 4,867 at the commit the section named). Also added: a property inventory that reconciles three documents which had been counting separately -- crossLink 1,977 (#763/#948), AIF attack 145 (#498 P1 closure), skos Walton mappings 70. It also corrects a near-miss of my own: `grep attackType` returns 0 because the properties are `aifAttackType`/`aifAttackedNode`, so the AIF layer IS serialized; the inventory is the only reliable measurement. And in §3.1bis: the "OWL can be regenerated post-tag" line is now done (#787), and the 46/1408 figure is marked as #753's deliverable rather than the current 145/1408. No verdict, status, arbitration or editorial content touched -- figures only, in the document's own dated-refresh style (v4, v4.1, v5, v5.1 → v5.2). Method rule recorded in the section: a byte-exact figure must name its commit AND its representation, a count must name its pattern. Otherwise the same object reads 1,407 or 1,408, and 1,081 or 1,977 or 1,985. Refs #134, #133, #763, #948 Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Un mot, pas un chiffre
Deux documents de release donnaient le même nombre avec deux unités :
CHANGELOG.md:61docs/RELEASE-NOTES-v0.9.0.md:23Un lecteur qui compare les deux voit une contradiction là où il n'y en a pas : 1985 compte les relations émises dans l'OWL, 1081 compte les cellules CSV non vides. Le nombre était juste ; c'est le mot « cellules » qui ne l'était pas.
Mesuré sur master avant d'éditer
crossLink_*non vides dansCards/Fallacies/Argumentum Fallacies - Taxonomy.csv, dont 137 multi-valuées (;) → 1230 cibles individuellesAnnotationPropertyaux 8 IRI crossLink dansdocs/ontology/argumentum.owl(match d'IRI exact)ObjectProperty, une par verbe → 1977 + 8 = 1985Deux notes d'instrument, parce qu'elles ont chacune failli produire un faux résultat :
grepsur le verbe nu compte la prose.mirrorsapparaît dans un exemple anglais ligne 28587 (« We've arranged the lighting and mirrors in our store… »). Il faut matcher l'IRI complet.docs/ontology/aif-export/README.md: « Raw parse = 1977 ≈ README 1985 (the -8 delta is one schema self-definition counted per verb, 8 verbs) ». Je l'ai re-dérivé par la mesure avant de lire la doc existante — l'ordre inverse aurait été plus économe. Le noter ici est plus utile que de le passer sous silence.Aucun chiffre n'est renuméroté.
1985reste la valeur établie : c'est celle qu'affirme le test passantLoadedOntology_ContainsCrossLinkAndAifAttackAssertions, et elle est employée de façon cohérente dansdocs/ontology/README.md, le certificat de publication #133, la validation du 12/07 etCHANGELOG.md:52. La toucher aurait été le vrai défaut.Diff
2 fichiers, 2 lignes.
docs/RELEASE-NOTES-v0.9.0.md— « 1985 cellules » → « 1985 relations émises … portées par 844 fallacies (59,9 % de 1408) », plus la mention des 1081 cellules source et du renvoi à la note de réconciliation. Les deux chiffres sont donnés côte à côte avec leur unité, puisque c'est leur coexistence qui déroutait.docs/taxonomy/498-reconciliation-p1-closure.md— « 1985 (59.9% of leaves) » → « 1985 emitted, carried by 844 leaves (59.9% of 1408) ». Le 59,9 % appartient à 844, pas à 1985.Aucun code, aucun CSV, aucune régénération. La porte de release #134 n'est pas touchée ; c'est une lisibilité de note de version à quelques jours du tag.
Refs #763, #133
🤖 Coordinator ai-01