docs: document UTS #39 confusables/homograph as explicit non-goal (PUNY-mjdrwxne)#20
Merged
Merged
Conversation
…NY-mjdrwxne) host_normalize() is not a safety gate. Add a normative Non-goals section to the normalization contract and a Non-goals section to the README stating that spoof / homograph / mixed-script / display-safety detection (UTS #39 / UTR #36) is explicitly not part of punycoder's acceptance criteria — "not part of the criteria", not "never relevant". Cross-reference UTS #46's own recommendation to apply those checks as application/UI-layer steps upstack. No behaviour change. Co-Authored-By: Claude Opus 4.8 <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
1 participant
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.
What
Item D of the standards-compliance audit (PUNY-emjvtzlr). Documentation only — no behaviour change.
host_normalize()is not a safety gate. This makes that explicit so nobody assumes normalization gives spoof protection:docs/normalization-contract.md): new normative Non-goals: spoofing and display safety subsection — confusable / homograph / mixed-script / display-safety detection (UTS #39 / UTR #36) is explicitly outside the acceptance criteria. A non-NAresult asserts validity + normalization under the pinned UTS #46 profile, nothing about visual safety.Both cross-reference UTS #46's own recommendation to apply UTR #36 / UTS #39 checks as application/UI-layer steps upstack — the argument for placing them in
rurlor a dedicated policy layer, not in the normalization primitive. Phrased as "not part of the acceptance criteria", not "never relevant".🤖 Generated with Claude Code