docs(changelog): drop two private-register codes a public standard ca… - #13
Merged
Merged
Conversation
…nnot resolve The compose-carry entry cited "the F8 / F2-value gap". Those are codes in a PRIVATE flaw register in another repository, which an external implementer reading this standard has no way to open — the exact bar this repo sets for every sentence it carries. The claim is unchanged and now complete on its own bytes. Founder's ruling the same day: "When a code is ambiguous, just remove the code altogether. No code is better than ambiguous code." Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
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.
…nnot resolve
The compose-carry entry cited "the F8 / F2-value gap". Those are codes in a PRIVATE flaw register in another repository, which an external implementer reading this standard has no way to open — the exact bar this repo sets for every sentence it carries. The claim is unchanged and now complete on its own bytes.
Founder's ruling the same day: "When a code is ambiguous, just remove the code altogether. No code is better than ambiguous code."
Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw