Tighten public evidence framing#34
Merged
Merged
Conversation
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.
Replaces remaining speculative/projected public documentation with evidence-backed release language.\n\nChanges:\n- replace projected 1990s performance section with measured QEMU era-profile evidence\n- remove alternate commercial/hardware timeline speculation from the long technical document\n- tighten README technical-innovation wording\n- update video plan thesis language\n- add a public hygiene test that rejects stale novelty-demo framing\n\nVerification:\n- stale phrase sweep over README/docs/gpt2_basic_documentation.md\n- python3 -m unittest tests.test_public_repo_hygiene\n- git diff --check\n- .venv-torch311/bin/python scripts/build_preview_release.py --self-test