Repository navigation
Kim Min Do under FAMILY_FIRST is told 'Do' was "read as a middle name" when it lands in the family #626
Description
An ambiguity's detail names the field its word was read as. Several reports word that from the role the word holds when the report is made, and a later step moves it:
| Input | Policy | Lands in | Report says |
|---|---|---|---|
Kim Min Do |
FAMILY_FIRST | family 'Do Kim' (P6 attaches Do) |
suffix-or-name: "read as a middle name rather than a post-nominal" |
Dr. de Mesnil Do |
FAMILY_FIRST | given 'Do' | "read as a middle name" |
Freiherr St John Smith MA |
default | family 'St John Smith' | title-or-name: "read as a given name by convention" |
Attorney General of Minnesota, Deputy Secretary of State |
default | family | "read as a given name by convention" |
Measured 2026-10-08: over the 1,536 corpus names under all three orders, those last two are the only corpus instances. #620's review found about 12k of the family-first kind on a generated grid, and about 60k of the "only name unit" kind. #614's second review fixed one instance of this class (Freiherr von Berg Ma) by moving the report to the stage that knows the outcome.
Fix direction: word the report from the token's FINAL role, which assemble knows, or move each emitter after the step that moves it. Add a guard: over a grid, every report's detail names the field its tokens land in (AGENTS.md's sweep paragraph).
Activity
Fix #626's review findings: the sixth emitter, P1's fold, a wider guard
Correct #626's recipe and A1's interacts list (third review)
Simplify #626's change: one swept-row list, shared helpers