Commit fe85bb3

Declined, measured: passing the whole name's fact to the view as well. It closes both (0 field and 0 report differences on a grid with one-word, two-word and titled heads) but the view also asks S6's credential lean, which P8 says is asked of the own words P3's span holds, and moving it there fails `test_a_maiden_clause_does_not_change_how_a_trailing_word_reads` (tests/v2/test_properties.py) on 270 of its 20,412 pairs (with it, `J. nee Smith BA` would read the credential where `J. BA` reads a name). Closing the gap needs the peel to take the numeral's case fact apart from the lean's — a design change beyond this fix.

Measured: the one-case grid gains `{a} {b} nee {n} {n}` and `{a} {b} nee j {n}`. ad486f66 disagreed on 36 of its 4,752 pairs, all in those shapes; this tree on none, and the fourth recorded control is that 36. 2.2.0 through 2.4.2 gave the lowercase reading above, and 2.0.0 and 2.1.0 the reading this restores (maiden 'x x'), so the release bullet for #723 carries this too. No corpus name moved.

- 2026-10-18 (Derek), #731 reverted — A MAIDEN CLAUSE'S NUMERAL IS NOT HELD TO ITS CAPITALS. The #731 entry above is superseded and its change reverted. Derek: this rule and maiden names do not really interact, because nobody writes a maiden marker followed by an initial, or two. Asked whether settling the gap that entry left open would simplify the parser, the answer was the opposite: it needs the peel to carry two case facts, one for S6's lean and one for the numeral. And #731 itself had bought `john smith nee x x` and `john smith nee j x` — both that unwritten shape — a case argument on `trailing_candidates`, a whole-name case test in the take, a stated exception to the candidates' superset contract (decisions/M2's #731 entry), two grid shapes and a second invariant with their controls, all reverted. The readings go back to 2.2.0 through 2.4.2's (`john smith nee x x` suffix 'x', maiden 'x', reported), stated as an Accepted clause of this rule with both spellings as examples. Kept from that PR: M2 naming S10 among the trailing rules its take asks, which was true before #731 and stays true. What this rule still says of a clause's letters — classify reads one by the whole name's case (the #723 code-review entry) — stands: the shape that guards is a connective inside a clause (`MARIA GARCIA NEE LOPEZ y FERNANDEZ`), which names do take.

run, written with a period or without, an initial being no shape

anyone writes there; behind a name word it is the generation

only when written bare, a period marking it the abbreviation of

generation slot still be open: where a further comma has already

named the suffix (C2), a single letter ending the GIVEN part has no

generation left to be, and stays a middle initial — with a

while adding a suffix comma after either turns that same letter

into the middle initial.

Signal: a neighbor: what stands before a one-character suffix word inside a comma part

it is.

"Smith, Esq." → suffix="Esq."

Signal: a shape: an unlisted word of two or more letters ending in its one period, opening the given-name part

"J. née Jones Smith V" → given="J." · boundary

"j nee smith" → given="j" · boundary

Signal: a count: one name word left beside a maiden name

where it fires, a family comma — a comma with a name segment

after it — silences it, a script whose own convention settles

the order (W4) silences it, and so does the word's own claim — a

nothing after it names no family and silences nothing, so

`سلمان،` and `Smith,` report where `Smith, Andrew` does not. A

comma with only a TITLE after it names no family either, but the

"abd née Jones" → ambiguities=()

"j" → ambiguities=()

Signal: a count: one name word that nothing else decided

a whole word and is not. The Irish Ó is never written with a

period, while Ó. is the initial of Óscar, Ólafur or Ólöf.

A one-letter word written with its period is an initial and not a

it is the particle. It is an initial in every position, so it

neither opens a surname, nor joins a chain, nor attaches to the

family behind a comma.

the particle. Such initials normally carry the period, and the

bare letter is exactly how the particle is written.

"Juan Ó Pérez" → middle=""

An `annotation` names a policy, locale (`[ru]`), or extras gate (`[ja+segmenter]`) in the registry beside the test. `· boundary` marks the non-firing example every rule must carry: an input shaped like the rule's subject where its effect does NOT occur. That is usually the rule's OWN stated exception — H1's given-name title, P3's single-letter carve-out — not an input the rule never reaches, so the exception is executable rather than merely asserted. Or the rule declares `no-boundary: <reason>` instead, so skipping the boundary is a recorded decision. `deviates:` states the INTENDED output on the example line while the marker records TODAY's output and the tracking issue; the runner asserts today's output strictly, so a parser change that closes the gap fails the suite until the marker is removed in the same PR. `grep -r deviates: docs/design/rules/` is the deviation backlog (deviations from statable rules — coverage gaps are a separate, larger category no grep can see, and contested vocabulary memberships a third, tracked as Open blocks keyed to the vocabulary set in decisions/).

Each rule's size is recorded, as a guard rather than a cap (mechanisms.md#RECORDED-ROSTERS). `tests/v2/rules_budget.json` holds each rule's statement word count (the Rationale counted, the Accepted clauses not), the statement's `except` and `unless` (a proxy for the clauses that carve out a case), its count of Accepted clauses (a line opening `Accepted:` or `Accepted,` — the rules write `Accepted, and …:`) and their words; `tests/v2/test_rules_budget.py` fails when a rule moves against its record, shrinking included, so the record follows a rule down. A rule that has to grow re-records with `uv run python -m tests.v2.rules_budget --record`, and the PR says so: the record's diff is where a reviewer sees the growth and asks what the new words read.

- [T2 — the katakana middle dot divides like a space](T2-katakana-middle-dot-divides-like-a-space.md)

- [T3 — the interpunct's flank guard](T3-interpuncts-flank-guard.md)

- [T4 — the bare letter as an initial](T4-bare-letter-as-an-initial.md)

up to X it does not, by their shape alone — unless the word in

front of it is written as an initial, which makes it a name word

too; in a name written wholly in one case a bare letter in front

numeral past X is a name word. A numeral of one letter needs

words to spare, as a bare ambiguous acronym does (S4): as the

second of two name words it is the family name, a title in front

as one with the numeral in front of it, the run taking both, as

1.4.0 read it.

"John Smith V Ph. D." → suffix="V Ph. D."