derek73#430 and derek73#432 are one boundary and land together. Inside a comma segment a roman numeral is read by WHAT STANDS BEFORE IT: Smith, PSM I given 'PSM' + suffix 'I' -> suffix 'PSM I' Smith, PSM I. given 'PSM' + suffix 'I.' -> suffix 'PSM I.' Smith, MD I title 'MD' + given 'I' -> suffix 'MD I' Smith, John V. suffix 'V.' -> middle 'V.' Smith, John V suffix 'V' -> unchanged, the boundary Behind a SUFFIX the numeral describes that suffix -- 'PSM I' is Professional Scrum Master level I -- so the run continues through it, period included, an initial there being no shape anyone writes. Behind a NAME the period is decisive: it marks an abbreviation, which is name material, so the numeral is the middle initial 'Smith, John B.' always was. Bare after a name it stays the generation (v1 parity, derek73#144), which is why the test is the period and not the numeral. derek73#430's cause was S2's initial veto in is_suffix_piece -- right after a name, wrong inside a credential run -- so the segment did not look like a run and fell to the given-and-suffix walk. One cause, two wrong answers: where the run's first word is TITLES vocabulary too the leading-title peel took it instead ('Smith, MD I' -> title 'MD', given 'I'), so a fix verified on PSM alone would have left that half broken and looked green. THREE readers, ONE reading. The gate that calls a segment a credential run, assign's router, and group's one-entry join must agree piece for piece; derek73#429 shipped the inverse of its own fix by deriving that agreement twice. segment_suffix_reading returns the per-piece verdicts and all three read it (mechanisms.md#ONE-PREDICATE-PER-QUESTION). The intermediate state proved the point: with only the gate and the router converted, 'Smith, PSM I' rendered 'PSM, I' -- roles right, render split, the same tell as derek73#429 one predicate along. Declined, and the v1 suite caught it: asking is_trailing_numeral_suffix for derek73#432's half. It answers the period question, but also refuses a numeral behind an initial-shaped piece -- a no-comma rule, and the opposite of this path's parity. 'Chang, Andy C I' is first 'Andy', middle 'C', suffix 'I', and asking it here made the numeral a middle. The derek73#401/derek73#421 entry records the same fork declining to transfer to this walk. Only the period half applies. Verification: suite 5702, mypy and ruff clean, differential 0 unexplained at 1.4.0, 2.0.0 and 2.1.0. Swept across all three name_orders -- identical, these being segment reads rather than positional ones. Both clauses mutation-checked: disabling derek73#430's kills three case rows, derek73#432's one. The corpus is not blind to the class. Three of 1072 names carry a comma then a word then a numeral -- 'Berg, abdul V', 'Smith, John I', 'Smith, John V' -- all BARE, the form deliberately left alone, so they are evidence the boundary held. 'Berg, abdul V' cannot reach the walk at all: the bound-given join makes 'abdul V' one piece, which is why the LENIENT mirror derek73#401/derek73#421 declined does not collide here. Not done, recorded rather than left implicit: neither half emits an ambiguity, though the no-comma 'John Smith V' reports suffix-or-name for the same fork. derek73#432 raises it as a secondary observation, and an emitter needs a trigger, a stage-ownership entry and a case row. Closes derek73#430 Closes derek73#432 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

FULL NAME	p_first	p_middle	p_last	p_suffix
MAIER, AMY LAUREN I	AMY	LAUREN I	MAIER
CHANG, ANDY CHUAN I	ANDY	CHUAN I	CHANG
CHUAN SUN, VIVIAN F I	VIVIAN	F I	CHUAN SUN
COVINO, PETER CARMINE III	PETER	CARMINE	COVINO	III

Issues with names in the format Last, First Middle Suffix where Suffix is I #144

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions