Soften README's framing of the piqc/ModelSpec relationship - #9
Open
paralleliq wants to merge 1 commit into
Open
Conversation
Remove the explicit "detecting drift between declared and actual" mechanism description and the three-layer system diagram — both described internal product methodology more specifically than an open-standard repo should, rather than just naming what ModelSpec is and does on its own. Co-Authored-By: Claude Sonnet 5 <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.
Summary
Why
Internal review flagged that this section described how the platform's detection mechanism works, not just what ModelSpec is — closer to methodology disclosure than the "name what exists" bar we want for this repo.
🤖 Generated with Claude Code