docs: approve filtered-word escaping as enumerated output facts - #375
Merged
Merged
Conversation
2 tasks
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.
Refs #374 (records the decision; the implementation stays open under #374).
Decision
opy-rs reproduces the pinned OverPy 9.7.10 filtered-word escaping (soft hyphen inserted into about 30 words, invisible formatting characters removed) for rule names and the
main.modeName/main.descriptionsettings strings, so this output converges structurally with the reference as goal principle 7 requires. Approved by the project owner in the #374 discussion.Changes
docs/adr/0007-filtered-word-escaping.md: the decision, including why the client's censor list (option C) cannot be the source and why keeping onlyrigger/admin(option B) is rejected.docs/compatibility/source-policy.md: new Enumerated output facts section. It admits a fact set that cannot be found by probing only when its content is fixed by the pinned output, an owner decision names it, the core holds an opy-rs-owned attributed representation, every entry is oracle-pinned (with a negative case for each whole-word match), and it changes only with a pin change. Only this word set is approved; it is no precedent for other upstream tables.docs/adr/README.md: index entry.Not in this PR
The implementation, its fixtures and the
docs/language-support/tooling-and-backend.mdstatus update, tracked in #374.Verification
Docs only.
git diff --checkclean; relative links and thelanguage-core.md#compatibility-targetanchor checked. The settings scope was confirmed against the pinned oracle:modeName: "Poland account"is written asP\u00adoland a\u00adccount, and native currently writes it unchanged.