Skip to content

docs(taxonomy): #499 AIF PR-1 (Virtues) — Raisonnement valide / Causalités cluster (proposition, gated) - #741

Merged
jsboige merged 1 commit into
masterfrom
docs/499-virtues-aif-mirror-schema-pilot
Jul 7, 2026
Merged

docs(taxonomy): #499 AIF PR-1 (Virtues) — Raisonnement valide / Causalités cluster (proposition, gated)#741
jsboige merged 1 commit into
masterfrom
docs/499-virtues-aif-mirror-schema-pilot

Conversation

@jsboige

@jsboige jsboige commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

What

#499 AIF chantier — PR-1 (Virtues side). Dispatch ompwhx [primaire] (ai-01). Proposition only — GATED, 0 write to prod CSV. Mirror of the po-2023 Fallacies chantier format (#498 PR-1 #699). This is the pilot for serializing the ratified AIF_attackType + AIF_attackedNode schema (#707 §4 Option a) on the Virtues side.

New doc: docs/taxonomy/499-aif-raisonnement-causalite-cluster.md (+108 lines, docs-only).

The cluster

Raisonnement valide (Virtues family 4) / Causalités bien identifiées (subfamily 4.1): anchor pk 80 + leaves 81/82/83. Chosen as the cleanest inverse-paradigm mirror — the Fallacies subfamily Causalité douteuse sits at path 4.1.x (698 Pétition de principe, 707 Inversion de causalité, 719 Effet cigogne), the Virtues subfamily Causalités bien identifiées sits at path 4.1. Same path prefix, opposite tenor — structural corroboration of jsboige's inverse paradigm, independent of the existing crossLink_Opposes mapping.

What this extends (not redoes)

The Virtues 12-col relational layer (crossLink_* + AIF_skos*) is already generated and validated CLEAN — 222/222 nodes, 9 PRs merged June 2026, validator #518 12/12 (see 499-virtues-parity-closure.md). This PR reuses that grounding (scheme, restored CQ, opposed Fallacy PKs) and only adds the I/RA/CA decomposition the newly-ratified schema asks for. No re-derivation.

The inverse-paradigm adaptation — FLAGGED for jsboige

The ratified columns are attack-shaped (attackType on attackedNode). A Virtue is the good holding of a scheme, not an attack. Three serialization options are documented in §3:

Option Virtue-side semantics Reco
A — "attack resisted" columns record the attack-type the virtue prevents + the node it holds (mostly undercut / RA-node) recommended
B — structurally empty columns empty (a virtue attacks nothing) loses the info
C — AIF-native support RA-node only, no attackType (would require fabricating a support token) violates #677

The pilot is written under Option A to make the proposition concrete (4/4 undercut on RA-node, consistent with jsboige's "most fallacies live in the undercut"). Only the last two table columns change if jsboige picks B or C. This is a judgment call on inverse-paradigm semantics — flagged for validation before the 222-row back-fill.

Why this matters (the EPITA consumer)

The harnais EPITA (2025-Epita-Intelligence-Symbolique) evaluates argumentation quality with 9 hard-coded virtues because it has no consumable Virtues backbone. The ratified I/RA/CA schema + this mirror give the quality axis the same verifiable mechanics as the fallacy axis (1408 nodes). Option A lets the consumer read, per virtue: which scheme it correctly holds, against which attack — the inverse of a fallacy row.

Proposition (Option A, per leaf)

pk title_fr RA-node (scheme held) CA-node resisted AIF_attackType AIF_attackedNode
80 Causalités bien identifiées (anchor) Cause to Effect causal RA held vs inversion/single-cause/correlation undercut RA-node
81 Indépendance des prémisses Argument from Rule rule RA held vs circularity (698) undercut RA-node
82 Causalité bien orientée Cause to Effect causal RA held vs direction inversion (707) undercut RA-node
83 Exclusion des causes alternatives Cause to Effect causal RA held vs spurious correlation (719/633) undercut RA-node

0 FAIL-LOUD in this cluster (every leaf has a native scheme + native attack-type). Honest scheme-divergence kept (pk 83 opposes cross-family 633 Relation infondée).

Discipline / gates

Asks for review

  1. Option A vs B vs C (§3) — the inverse-paradigm adaptation. My recommendation is A; jsboige's call.
  2. Once Option is ratified: the 222-row back-fill is largely mechanical (attackType/attackedNode derivable from scheme + opposed-family via the existing 12-col annotations) — a single programmatic back-fill PR is plausible.

Relates: #499, #498 (po-203 Fallacies owner), #707 §4 (ratified schema), #677 (0 fabrication), #518 (validator), 499-virtues-parity-closure.md, 499-virtues-prod-write-spec.md, 498-coverage-status.md.

Co-Authored-By: Claude-Code noreply@anthropic.com

…e / Causalités cluster (proposition, gated)

Pilot for serializing the ratified #707 §4(a) schema (AIF_attackType +
AIF_attackedNode) on the Virtues side, mirroring the po-2023 Fallacies chantier
format (#498 PR-1 #699). Dispatch ai-01 ompwhx [primaire] #499 Virtues AIF.

One cluster modeled: Raisonnement valide (family 4) / Causalités bien
identifiées (subfamily 4.1) — anchor pk 80 + leaves 81/82/83. Chosen as the
cleanest inverse-paradigm mirror: the Fallacies subfamily Causalité douteuse
sits at path 4.1.x (698/707/719), the Virtues subfamily sits at path 4.1 —
same path, opposite tenor (structural corroboration of jsboige's inverse
paradigm, independent of the crossLink_Opposes mapping).

The Virtues 12-col relational layer is already generated + validated CLEAN
(222/222 nodes, 9 PRs merged June 2026, validator #518). This PR does NOT redo
it; it extends it with the I/RA/CA decomposition the ratified schema asks for,
reusing the existing scheme/CQ/opposed-PK grounding (no re-derivation).

Inverse-paradigm adaptation FLAGGED for jsboige validation (not decided alone):
the ratified columns are attack-shaped, but a Virtue is the good holding of a
scheme, not an attack. Three options documented (A attack-resisted [reco],
B structurally-empty, C AIF-native support). Pilot written under Option A;
only the last two table columns change if jsboige picks B or C. 0 fabrication
(undercut + RA-node are native AIF). Native vocab only (discipline #677).

0 prod CSV write, 0 DB, 0 OWL regen, 0 Cards/. Proposition doc only.

Co-Authored-By: Claude-Code <noreply@anthropic.com>
@jsboige
jsboige merged commit 684720d into master Jul 7, 2026
3 checks passed
@jsboige
jsboige deleted the docs/499-virtues-aif-mirror-schema-pilot branch July 7, 2026 11:11
jsboige added a commit that referenced this pull request Jul 7, 2026
… (Option A, HOLD prod) (#744)

Specifies the deterministic derivation of the 2 new columns (AIF_attackType +
AIF_attackedNode, schema #707§4 Option A ratified) for all 222 Virtues nodes,
from the existing 12-col relational grounding (phase-2, CLEAN 222/222 #518).

Generalizes the method validated on 3 clusters (PR #741/#742/#743, 9 leaves,
14 fallacy-instances) into a programmable 2-step rule:

1. DEFAULT = undercut/RA-node (the inference is broken — credibility, bias,
   causal link, tool-misuse, commitment short-circuit). Covers ~95% of nodes.
2. OVERRIDES (rare):
   - undermine/I-node: fallacy asserts a known-false proposition (889 Mensonge,
     9 nodes clean; 804 Acception arbitraire borderline, 4 nodes, conservative
     default undercut/RA unless per-case override).
   - rebut/CA-node: EMPTY SET — scan of all 60 opposed fallacies = 0 occurrences,
     confirms rebut-rarity finding (PR #743 §3) at full scale.

Expected output distribution: ~209-213 undercut/RA + 9 undermine/I (889) +
0-4 borderline (804) + 0 rebut/CA.

Includes: full-scale scheme distribution (14 families), override tables with
false-positive exclusions (644/727/735/750/942/974/1287 = tool-misuse/credibility
→ undercut/RA, NOT undermine), programmatic apply-script pseudo-code (ready to
execute), anti-drift gating sequence (0 write until po-2023 column contract #498
lands on master + ai-01 review), validation checklist (fail-loud conditions).

KEY LOAD-BEARING OUTPUT for ai-01/jsboige: AIF_attackType column will be
undercut-dominated ~95%. Don't over-invest rebut/undermine coverage in validator
tooling — their rarity is the domain's real structure, not a modeling gap.

DISCIPLINE:
- HOLD prod-CSV write per ai-01 order (anti-drift vs po-2023 column contract).
- 0 fabrication (#677), 0 write CSV/DB/OWL/Cards. Docs-only.
- Reuses CLEAN 12-col grounding, does not re-derive.

Co-authored-by: Your <your.email@example.com>
Co-authored-by: Claude-Code <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant