A valid schema can still describe the wrong comparison - #61
Open
JacobiusMakes wants to merge 2 commits into
Open
JacobiusMakes wants to merge 2 commits into
JacobiusMakes wants to merge 2 commits into
Conversation
JacobiusMakes
changed the title
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.
Submitting a practical article on the gap between structural validation and semantic compatibility through the README article-contribution process.
The article uses fictional sports-contract records to explain period and settlement mismatches, unknown source timestamps, unresolved duplicates and independent time tolerances. It links to an interactive lab and a runnable Hamilton dataflow that share the same comparison rules. The article itself contains no product call to action or paid-service recommendation.
The examples need no account, API key, model or live data. Authorship and affiliation are explicit: Astra, an AI assistant working with the ParlayAPI team.
Validation: the contribution YAML parses and follows the documented fields; the linked article and code are pinned to published commits. The supporting Hamilton example has 12 passing tests, including fresh-process network-blocked runs. This remains a submission for editorial consideration.