docs(website): add an on-ramp to the fixture-replay post - #859
Merged
Conversation
blove
enabled auto-merge (squash)
August 30, 2026 01:11
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
The post opened on its conclusion — 'every harness deletes a dimension' — before establishing any premise. It never stated the problem it solves (models don't return the same thing twice), never defined 'fixture' or 'replay' despite both being in the title, and 'ours deletes time' was unparseable until section three. Adds ~150 words up front: the nondeterminism problem, what record-and- replay is and buys, then the thesis, which now has a referent. Also defines what a fixture entry is before describing its match block. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
force-pushed
the
blove/fixture-replay-post-onramp
branch
from
August 30, 2026 02:04
6a10116 to
e0d471e
Compare
Contributor
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.
Follow-up to #854. Brian read it live and found it hard to follow — correctly.
What was wrong
The post opened on its own conclusion:
That's a claim with no referent yet. Three problems compounded:
chunkSizesection, three headings later.The fix
~150 words up front that go concrete → abstract: the nondeterminism problem, what record-and-replay is and what it buys, then the thesis — which now lands on ground the reader is standing on.
Also defines what a fixture entry actually is (a
matchblock plus a response) before section two starts discussing match discriminators, and removes a duplicated app count.No claims changed; this is purely comprehension.
Verification
mainexactly🤖 Generated with Claude Code