Document cross-language semantic parity matrix - #367
Merged
Conversation
Contributor
|
uriahf
marked this pull request as ready for review
August 21, 2026 11:13
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.
Goal
Record the Stage 2 R/Python semantic parity conclusions after the merged Stage 0 contract and Stage 1 characterization tests.
What this adds
Adds
PARITY.mdwith:reference_groupas compatibility terminology rather than the target domain abstraction;rtichoke_vizshould remain unchanged until package-level semantics are aligned.Scope
Documentation-only. No statistical calculations, public APIs, tests, production behavior, generated documentation, or
rtichoke_vizare changed.Paired with uriahf/rtichoke#165.