docs(taxonomy): #499 Virtues scale-up phase 2 batch 1 — Langage exact depth-3..4 leaves (gated) - #530
Merged
Merged
Conversation
… depth-3..4 leaves (gated) Phase 2 begins the depth-3..7 leaf layer (194 nodes). This batch 1 covers the smallest family, Langage exact (14 nodes: 9 depth-3 + 5 depth-4), as a calibration batch for leaf-level granularity. Same method, schema, and anti-fab guarantee as Phase 1 (#510, merged 0ad4025): - gpt-5.5 /v1/responses reasoning:low, grounding catalog of 7 family PKs + 63 real depth-3 fallacies (forbidden to use any PK outside it). - Family mirror as hard constraint: every Langage-exact leaf -> Abus de langage (PK 798). - Three independent verification layers re-checked against the REAL corpus (not the prompt catalog): catalog membership, ground-truth PK<->text_fr on the 1408-row Fallacies CSV, mirror consistency. 14/14 annotated, 0 violations. - Anti-fab validator #518 (kind=virtues): CLEAN — 14 rows, 0 HARD, 0 WARN. Granularity refinement for leaves: a depth-4 virtue opposes the most specific applicable fallacy under the family (e.g. "Ponctuation correcte" -> Amphibologie 847, not a broad ambiguity). GATED proposal — docs/taxonomy/ only, no production Virtues CSV change. 6 families (180 nodes) remain for subsequent phase-2 batches. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
clusterManager-Myia
left a comment
clusterManager-Myia
left a comment
Collaborator
There was a problem hiding this comment.
[NanoClaw]
LGTM. Calibration batch propre — même méthode/schema/anti-fab que Phase 1, validator CLEAN sur 14 rows, gated proposal (pas de touch prod). Les 14 depth-3/4 leaves sous Langage exact → Abus de langage (798) sont cohérents avec la structure Phase 1. Les opposed fallacies PKs sont plausibles et spécifiques au niveau feuille (bonne granularité). La doc scope/gate boundaries est claire. Ready pour jsboige validation.
jsboige
added a commit
that referenced
this pull request
Jun 18, 2026
…matique depth-3..4 leaves (gated) (#532) Phase 2 batch 2: the Rigueur mathematique family (16 leaves: 9 depth-3 + 7 depth-4). Same method, schema, and anti-fab guarantee as batch 1 (#530, merged fc2013f) and Phase 1 (#510). - gpt-5.5 /v1/responses reasoning:low, grounding catalog of 7 family PKs + 63 real depth-3 fallacies (forbidden to use any PK outside it). - Family mirror hard constraint: every Rigueur-mathematique leaf -> Erreur mathematique (PK 594). - Three independent verification layers re-checked against the REAL corpus: catalog membership, ground-truth PK<->text_fr on the 1408-row Fallacies CSV, mirror consistency. 16/16 annotated, 0 violations. - Anti-fab validator #518 (kind=virtues): CLEAN — 16 rows, 0 HARD, 0 WARN. Depth-4 leaves oppose the most specific applicable math fallacy (e.g. "Exactitude numerique" -> Erreur de calcul 681 + Imprecision 667, not a broad sampling fallacy). "Sign" scheme dominance reflects the probabilistic nature of most math-rigor virtues. GATED proposal — docs/taxonomy/ only, no production Virtues CSV change. 5 families (164 nodes) remain for subsequent phase-2 batches. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Jun 18, 2026
jsboige
added a commit
that referenced
this pull request
Jun 22, 2026
…lot diacritics (#578) Add the closure dossier for #499 (Virtues relational/AIF parity) and normalize the pilot CSV's display diacritics, giving ai-01/jsboige one consolidated, validator-clean dossier to review. Context: ai-01 dispatched GO #499 (relational layer, draft non-prod, docs/taxonomy/, gpt-5.5). Verify-before-code showed generation was already COMPLETE: pilot (#503) + phase 1 (#510) + phase 2 batches 1-7 (#530-#544) cover all 8 Virtue families depth 1-7. So the genuine remaining un-gated work was consolidation + validation, not generation. Coverage (measured against the real 223-row Virtues CSV): - 223/223 Virtue PKs annotated (0 unannotated) = 100% coverage. - 222 annotation rows across 12 CSVs (pilot + phase 1 re-confirm roots). - 14 distinct Walton schemes referenced (Rule 50, Commitment 40, Bias 27, Sign 26, Verbal Classification 21, ...) - semantic specificity, not template repetition. - 7 Virtue families -> 6 Fallacy families (Presentation intregre 34 + Honnetete 152 both -> Tricherie 887, the dual-facet mapping gpt-5.5 recovered independently). Validator #518 holistic run across all 12 CSVs: - BEFORE: 12/12 CLEAN, 0 HARD, 8 WARN (all in the pilot CSV #503). - The 8 warnings were cosmetic diacritic-folding in the pilot's display columns (virtue_title/prevented_family_name/opposed_fallacies_readable): "Premisses fiables" vs corpus "Premisses fiables" (ASCII-folded). PKs, Walton schemes, CQs were all real and verified - WARN, not HARD. - This PR normalizes the pilot display diacritics to the corpus (aligning it with its own pilot MD section 4 table, which already shows accented forms). No PK, scheme, CQ, link_type, or justification changed. - AFTER: 12/12 CLEAN, 0 HARD, 0 WARN. Closure recommendation: CLOSE #499 (content-proposal layer). Generation complete, 100% coverage, 0 HARD violations, fail-loud satisfied. Remaining steps are all GATED on jsboige: (1) content validation, (2) prod 12-col Virtues CSV write, (3) OWL propagation (Virtues not yet in OWL export - OwlAdapter handles Fallacies only), (4) EPITA consumer wiring. New file: docs/taxonomy/499-virtues-parity-closure.md (mirrors 498-aif-closure.md structure). Modified: 499-pilot-annotations.csv (display diacritics only). No production Virtues CSV touched. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude Opus 4.6 <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
2 participants
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
#499 Virtues scale-up — Phase 2, batch 1:
Langage exactfamily (14 depth-3…4 leaves).Phase 1 (#510, merged
0ad40259) completed the depth-2 backbone. Phase 2 begins the depth-3…7 leaf layer (194 nodes total). This is batch 1 — the smallest family,Langage exact(14 nodes) — a calibration batch for leaf-level granularity before the 6 larger families follow.Method — identical to Phase 1 (#510), verified
/v1/responsesreasoning:low, grounding catalog of 7 family PKs + 63 real depth-3 fallacies (forbidden to use any PK outside the catalog).Langage exactleaf →Abus de langage(PK 798).text_frcharacter-for-character.prevented_family_pk= 798.tools/validate_taxonomy_annotations.py, kind=virtues):✓ CLEAN — 14 rows, 0 HARD, 0 WARN.Granularity refinement (leaf-level)
A depth-4 leaf opposes the most specific applicable fallacy under the family — e.g. "Ponctuation correcte" (pk 149) →
Amphibologie(847) +Ambiguïté narrative(876), not a broad ambiguity. This is the depth-3+ calibration Phase 1 predicted (phase-1 §7.2).Files
docs/taxonomy/499-virtues-scaleup-phase2.md— proposal (method, scope, anti-fab, the 14 rows).docs/taxonomy/499-scaleup-phase2-annotations.csv— 14 rows, 10-col presentation schema (same as Phase 1).Gate boundaries (HARD, all respected)
Argumentum Virtues - Taxonomy.csvchange —docs/taxonomy/only.tmp/, not committed) — same as Phase 1.GATED proposal — worker signals structure + grounding; ai-01 spot-checks, jsboige validates content.
🤖 Worker po-2024