docs: finish retiring the freeze vocabulary from canon - #1087
Merged
Conversation
The earlier change corrected the authoritative sources — api-stability.md, the scripts, the docs page, RELEASING and PUBLISHING — but left the wording in nine other canonical documents. Those still described 'the freeze contract' and 'the frozen surface': a promise the project had already stopped making, which is exactly the drift the original change existed to stop. Fifteen replacements across nine files. All now say protected or removal-protection. Four uses are deliberately untouched, because the word means something different in each: Object.freeze'd policy clones in agent-safety-model.md, 'freeze the sim' for reduced motion in host-model.md, 'frozen particles' in the poster render mode, and 'frozen design history' for the planning archive. A regex sweep would have damaged all four, which is why this was done by reading rather than by substitution. One use of 'freeze' survives on purpose: api-stability.md's own sentence saying it is not one. check:links and check:docs clean.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Why
The earlier change corrected the authoritative sources —
api-stability.md, the scripts, the docs page,RELEASING,PUBLISHING. It left the wording in nine other canonical documents, which still described "the freeze contract" and "the frozen surface."That's a promise the project had already stopped making — exactly the drift the original change existed to stop.
What changed
15 replacements across 9 files. All now say protected / removal-protection:
README.md·agent-safety-model.md·common-mistakes.md·computational-interaction-alignment.md·deprecation-plan.md·documentation-standards.md·platform-architecture.md·substrate-api.md·substrate-overview.mdFour deliberately untouched
The word means something completely different in each, and a regex sweep would have broken all four:
agent-safety-model.mdObject.freeze'd policy cloneshost-model.mdvisualization-methods-taxonomy.mdREADME.mdDone by reading rather than substitution, for that reason.
One use of "freeze" survives on purpose:
api-stability.md's own sentence saying it is not one.Gates
check:links·check:docs— clean.