Read a Turkic marker ending three name words with the father's name as the family (#1187) - #1366

Closes #1187. Refs #1253.

Under Turkic handling (locales.TR_AZ, or PatronymicRule.TURKIC), a name of exactly three name words that ends in a standalone patronymic marker now reads the father's name and the marker together as the family. The patronymic view already held the same two words.

from nameparser import parser_for, locales
n = parser_for(locales.TR_AZ).parse("Бекмырза Чолпонбай уулу")
n.given, n.family, n.patronymic   # ('Бекмырза', 'Чолпонбай уулу', 'Чолпонбай уулу')

1.4.0 (with Turkic handling) through 3.0.1 read middle Чолпонбай, family уулу. The group suggester now votes Turkic for the same shape, so a list of such names gets the rule.

This is the second leaf of #1253's decision. Its first statement: family is the name a convention files a person under, and a Kyrgyz name with no surname files under Father uulu.

The rule (rules/O2, the Turkic rotation)

• Scope. It keeps the four-word rotation's scope: no comma, the default given-first order standing (a declared family-first order stands, as O1's scope says), and titles, suffixes and nicknames aside.
• The marker must be the last name word. The code checks this by position as well as by role. With the East Slavic rule also on, O1 may have rotated a marker-first name (Уулу Аскар Бакытович keeps family Уулу, patronymic Бакытович). Review found that the first version got this wrong.
• Unchanged shapes (each a boundary example in rules/O2 and a test row):
  • two name words: Cavad oğlu → family oğlu;
  • five or more;
  • a given name that P5 binds from two words: Abdul Rahman Ahmad oglu → family oglu;
  • a suffix comma: Aidai Mederbek kyzy, PhD → family kyzy.
• Precedence over O6. The middle word is taken first, so under two_family_names Ali Hasan oglu reads one family unit (surname1 Hasan oglu) where it read two.
• The old O2 boundary example "Ali Ahmad oglu" [tr_az] → family="oglu" moves. Its 2026-07-02 decisions entry gets a superseded note, not a rewrite.

Gate: measured before the code (2026-11-12)

All parliament figures in this PR are from the opensanctions-parliaments fetch of 2026-11-12 (23 datasets, 24,066 names). The Turkic chambers' counts are the same as in the 2026-11-08 fetch. Other figures come from the fielded local corpora:

• No chamber writes a two-word or a five-word name ending in a marker.

Decisions for the maintainer

1. Azerbaijani (Should a Kyrgyz name read Father uulu as the family? (Бекмырза Чолпонбай уулу gives family уулу) #1187's first question). No cached source writes Given Father oğlu without a surname except JRC's Russian spelling of Polad Bülbüloğlu, whose surname is exactly the father's name and the marker. Nothing measured argues for splitting the rule by language, so it reads all Turkic markers alike.
2. Two words (its second question) stay as they were:
   • PSC's Turkish Ahmed Oglu and ORCID's Gunel Kizi file the marker as the surname.
   • R9 already reads a two-word name whole as the patronymic.
3. Five words: no instance anywhere, so they keep the positional reading.
4. The group suggester votes where the rule reads, as decided in coordination: one condition in _suggest._patronymic, so a three-word name with the marker last votes Turkic. Edge rows cover two, three, four and five words, a family comma and a maiden clause. A maiden clause already voted on master, through the four-word shape, and R9's Turkic arm reads it. Nothing else in _suggest.py changes; the Should an ALL-CAPS word in a mixed-case name mark the family name? DUPONT Jean gives given DUPONT #659 worker's second PR touches a different function there.
5. Matching cost. Under the pack, a father's name written as an initial now conflicts: Ali Ahmad oglu / Ali A. oglu reads family family-initial, which is opt-in. Before, the initial sat in the middle and the pair was consistent. In exchange, Ali Ahmad oglu / Ali Ahmad and the Kyrgyz name with or without its marker become consistent (part-of-other).

What moved

• Corpus readings. Ran config_diff.py diff default plain:TR_AZ plain:TR_AZ+RU --committed --local all --match <the marker alternation stated in decisions/O2> with --readings in both trees and compared line by line, over the 947 names both trees hold.
  • Default: 0 moved.
  • TR_AZ: 489, every one middle → family. 468 are Kyrgyz; the rest are Uzbek, Kazakh and Azerbaijani names of the same shape, plus the committed conventions row Ali Kara Oğlu.
  • TR_AZ+RU: the same 489.
• Field agreement, local_agreement.py --locale tr_az --base <master>:
  • PSC: 16 progress, 0 regressions.
  • PatentsView: no change.
  • ORCID: 458 progress, 2 regressions, 4 changed. The 2 regressions are holders who put the father's name in the given box and the marker alone in the family box.
• CLDR per-pack view: TR_AZ 39/48, unchanged.
• Snapshot: no reading moves. It gains the new rules examples' default readings, from the rules-corpus rebuild.
• suggest_measure.py --base (this tree's comparator on both sides): 5 cells moved, none in the population rows (the same-order rows are unchanged).
  • The TURKIC table's kg_jogorku_kenesh row: {T} and {E,T} 86/90 → 90/90.
  • kg_jogorku_kenesh's rule votes, 85 for and 0 against → 85 for and 4 against, under both bases. The list is still decided East Slavic.
  • id_dpr's 0/0 → 0/1 under both bases (Y. JACKI ULY), still undecided.
  • The comparator changed too. A family-last list's name had been scored by its last word, the marker alone; it now takes the father's name and the marker for a three-word name ending in one. So against the table recorded in decisions/group-suggestion, nothing, {E} and suggest read 86/90, and {T} and {E,T} stay 90/90.
  • The harness proof holds: every row written against its base reads 0%, and every row in its base's order 100%. No figure quoted in Parser.suggest's docstring, docs/suggest.rst or decisions/group-suggestion moves.

Checks

• uv run pytest with the ja extra, on the head: 46,055 passed. Without it, on the first commit: 45,999 passed. Python 3.15 in its own environment: 45,999 passed.
• uv run pytest -n0 -m serial: 35 passed.
• uv run mypy, uv run ruff check, tools/vocab/build.py --check: clean.
• sphinx-build -b doctest docs and -W -b html: clean.
• Every condition of the new branch has a row in _TURKIC_THREE (tests/v2/pipeline/test_post_rules.py) or a test beside it that fails when the condition is removed. Each was checked by mutation.

Reviews

Each review ran as a subagent in its own detached worktree on the pushed head, with a read-only master checkout beside it.

🤖 Generated with Claude Code