Repository navigation
Close #752's open questions in decisions/ and point the title words left at #913 - #918
Merged
Merged
Conversation
…eft at #913 Phase 2's sub-phases have all landed. Four `Open:` lines in decisions/ and H1's still cited #752 or the closed #348: - O6: the question parked on #752, whether two_family_names reports the reading it did not take, is decided: it reports nothing and surfaces no alternative, since the caller declared the convention (Derek, 2026-10-27). A Standing line and a dated entry replace the Open line. - suffix-acronym-collisions and vocabulary-collisions: the Open lines become Elsewhere pointers to phase 2a's derived markers and to H9's report entries; vocabulary-collisions and H1 point at #913. - vocabulary-model: Open drops #752 for #913. - The RFC notes phase 2 complete and points 2j's row at #913. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 2 (#752) is complete: every sub-phase, 2a to 2m, has merged. Before the issue closes, this updates the decisions
Open:lines that still pointed at it, or at the closed #348. It changes no parser behavior.O6, two family names. The question parked on Phase 2: derive ambiguity from clashing readings and extend the gate to every reading kind #752, whether
two_family_namesreports the reading it did not take, is decided: it reports nothing and surfaces no alternative, since the caller declared the convention.Ambiguity.alternativerides on a report, so the switch carries none. A Standing line and a dated 2026-10-27 entry replace the Open line.suffix-acronym-collisions. Its Open line becomes an Elsewhere pointer to phase 2a, which derived the ambiguous marking from name readings and moved no membership.
vocabulary-collisions. Its Open line becomes an Elsewhere pointer:
A new
Open: #913names the title words left.H1. Its Open line points at Should Baron, Bishop, Judge and the other title words borne as names read as names outside a title phrase? (
Baron Davis→ title 'Baron', no given name) #913 instead of Should a word that is both a title and a given name report an ambiguity? (Baron Davis→ title 'Baron', no given name) #348.vocabulary-model. Its Open line drops Phase 2: derive ambiguity from clashing readings and extend the gate to every reading kind #752 for Should Baron, Bishop, Judge and the other title words borne as names read as names outside a title phrase? (
Baron Davis→ title 'Baron', no given name) #913.The RFC. It notes Phase 2 complete and points 2j's row at Should Baron, Bishop, Judge and the other title words borne as names read as names outside a title phrase? (
Baron Davis→ title 'Baron', no given name) #913.A design-docs review found three defects in the first draft, all fixed here:
title-or-name;Baron Davis→ title 'Baron', no given name) #348's answer to the wrong entry;The design-doc tests pass.
🤖 Generated with Claude Code