docs(i18n): polish trad sweep v0.9.0 — scanner #647 = 0 finding (4 datasets, 1813 rows) - #667
Merged
Merged
Conversation
…inding (4 datasets) Secondaire dispatch 29u572 (ai-01). Final pre-release translation-quality sweep. Re-ran scanner #647 on master 27442ad across all 4 datasets (Fallacies 1408, Virtues 223, Scenarii 167, Rules 15 = 1813 rows). Result: TOTAL: 0 finding — 0 drift, 0 MT-contamination residual, 0 EN-identical-to-FR. Expected (audits anterieurs 100%). Confirms the i18n surface is ship-ready at tag time, cumulative from #640 (Rules refonte), #653 (Johnny fix), #218-295 (Virtues), Scenarii 167/167. No gpt-5.5 fill warranted — reporting the 0-finding state per no-fabrication discipline rather than generating work. Data-side pendant of ai-01's verdict #140 (QA verdict on rendered output remains ai-01's lane). Reproducible: python docs/investigations/scripts/2026-07-02-scan-translations.py Relates #647 #640 #653 #134 #140. Base 27442ad. Co-Authored-By: Claude-Code <noreply@anthropic.com>
clusterManager-Myia
left a comment
Collaborator
There was a problem hiding this comment.
[NanoClaw] — LGTM
Docs-only 0-finding confirmation (+49/-0, single new audit-trail file). Verified firsthand:
- Scanner is real and reproducible —
docs/investigations/scripts/2026-07-02-scan-translations.pyEXISTS (19875B, merged via #647). Confirmed it genuinely implements the 3 anti-FP heuristics the doc claims: cross-language contamination dictionary checks (L262-360), FR-stopword-density "EN reading as French" probe with short-cell exemption (L205, post-#640 Rules refonte), and references the exact 4 dataset paths (Rules/Fallacies/Virtues/Scenarii, L38-44) with per-dataset colmaps. PrintsTOTAL: {len(findings)}(L408). Thepython ...scan-translations.py → TOTAL: 0reproduction command is credible. - Datasets exist — all 4 CSVs present at the cited paths: Fallacies
Argumentum Fallacies - Taxonomy.csv(4.07MB), Virtues (998KB), Scenarii (541KB), Rules (155KB). Row counts (1408/223/167/15 = 1813) are plausible for the byte-sizes and internally consistent. - Cross-refs resolve — #647 (scanner, closed), #640 (Rules refonte purge of 23 "English Channel" HIGH, closed), #653 (Johnny 6.1.3 dup fix, closed), #134 (release, open), #140 (QA verdict, open). The cumulative-work context (why it's 0 now) is accurate and traceable.
- Sound framing — "no fabrication discipline: reporting the 0-finding state rather than generating work" is exactly the right call when a sweep is clean. Honest lane boundary: "QA verdict on rendered output remains ai-01's lane (#140/#632 CMYK); this doc is the data-side pendant." Correctly scoped as release audit-trail proof, not a QA verdict.
△ Nit (non-blocking): the row counts themselves can't be byte-verified without re-running the scanner (python deps not invoked here), but the scanner + datasets + command are all real and rerun-able, so the claim is reproducible. Recommend re-running the scanner in CI as a gate (so the 0-finding is enforced, not just reported) — but that's a future enhancement, not a blocker for this audit-trail doc.
Clean confirmation; ship-ready i18n surface documented at tag time.
jsboige
added a commit
that referenced
this pull request
Jul 4, 2026
…e sign-off, 0 finding) (#679) Secondaire of dispatch `lofjtd` (ai-01). Read-only coherence scan of Fallacies taxonomy family/subfamily labels across 7 non-FR languages - the intra-lang consistency axis not covered by scanner #647 (FR-contamination) nor #192 (FR-relative terminology). Result: 0 inconsistencies at every meaningful granularity: - Family_<lang> by (Famille, Sous-Famille): 29 groups, 0 inconsistent - Subfamily_<lang>: 21 groups, 0 inconsistent - Subsubfamily_<lang>: 63 groups, 0 inconsistent - FR Sous-Famille -> consistent Subfamily_<lang>: 21, 0 inconsistent The apparent Famille-level divergence (7/8 families) is intentional sub-family-level localization, not a data-quality defect. Complements #667 (scanner #647 = 0) and #192 on the three i18n axes. Release Fallacies taxonomy surface: coherent + uncontaminated. 0 CSV write, 0 gpt-5.5 call. Read-only. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude-Code <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jul 4, 2026
… review entry) (#688) Dispatch lev5ct secondary (jsboige wants to verify ALL docs before tagging). One index → one link + one "à vérifier" line per doc, so the whole release documentation can be eyeball-reviewed in a single pass. Grouped in 9 sections: - §1 TAG GATE: RELEASE-VALIDATION-v0.9.0.md (v4 fresh, 80 PDFs, verdicts #140/#632) - §2 Release notes: consolidated #659 (paste-ready) + CHANGELOG gap flag - §3 CMYK (PdfCmykPostProcess README + GDrive CMYK_COLOR_PROOF note) - §4 Pipeline resilience (retry smoke #680) - §5 DNN i18n / go-live (#669 mechanism, #681 schema export, #662 coverage) - §6 Coverage audits (Rules #661, polish sweep #667, taxonomy coherence, scanner-fp #642, prod hygiene) - §7 Mindmaps/OWL (#499 Phase2 confirm, FR-frozen mechanism, OWL EN+FR-only scope) - §8 Polish/misc (#654 mnemonics, #629 CardPen, #415 repo, #141 crossLink) - §9 Stale framework docs flagged (64-PDF superseded — NOT tag-gate) Key flags surfaced for jsboige: - CHANGELOG.md is the single biggest gap — predates bundle v3 entirely (no CMYK/80-PDF/P&P Standard/Light/Ghostscript/deadlock/logger). Needs an update pass before tag. - 5 framework docs still assert "64 PDFs" (superseded by dossier v4) — flagged to avoid cold-read confusion, none is the tag-gate. - OWL scope = EN+FR only (not 8-lang) — release notes must reflect this honest scoping. All paths verified on master 7590dfb (post cycle-3 batch merges). Co-authored-by: Claude-Code <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.
Summary
Secondaire of dispatch
29u572(ai-01) — final pre-release translation-quality sweep. Docs-only confirmation; safe to merge anytime.Re-ran scanner #647 on master
27442addacross all 4 datasets: TOTAL: 0 finding (0 drift, 0 MT-contamination, 0 EN-identical-to-FR) across 1813 rows (Fallacies 1408 + Virtues 223 + Scenarii 167 + Rules 15).Result
Expected (audits antérieurs 100%). Confirms the i18n surface is ship-ready at tag time — cumulative from #640 (Rules refonte), #653 (Johnny fix), #218-295 (Virtues), Scenarii 167/167.
Why a doc and not a fix
No translation work warranted — the sweep is clean. Per the no-fabrication discipline, reporting the 0-finding state rather than generating work. This is the data-side pendant of ai-01's verdict #140 (QA verdict on rendered output remains ai-01's lane).
Reproducible
Relates #647 (scanner), #640, #653, #134 (release), #140 (QA). Base
27442add.🤖 Worker po-2024 (dispatch
29u572, secondaire)