docs: drop redundant sustained scenario from single-client retry demo#112
Merged
Conversation
…ry demo Retry can't help the caller on a sustained outage, so its counters read plain ✗82 vs httpware ✗81 — "no difference" at a glance, against the suite's one-number-that-pops design, and its stop overclaimed a "fails fast" that never showed (budget-exhausted requests count as ✗, not fast-fail). Keep only the Brief blip scenario (clear ✗6 vs ✗0 win); the herd view below now owns the sustained/amplification story with numbers that pop (~18x vs ~3x). Preserve the "retry rescues blips, not outages" point as one line of the herd intro. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
The single-client retry demo's Sustained outage scenario showed plain ✗82 vs httpware ✗81 — near-identical, which reads as "no difference" at a glance. That's correct model behavior (retry can't rescue a caller from a sustained outage), but it works against the suite's design where every scenario spotlights a number that pops, and its stop copy overclaimed a "fails fast" that never showed (a budget-exhausted request still hits the backend once and counts as ✗, so the fast-failed counter stays 0).
Rationale + details:
planning/changes/2026-07-19.03-drop-single-client-sustained-scenario.md.Change
sustainedscenario from the single-client retry demo, leaving only Brief blip (self-evident win: plain ✗6 vs httpware ✗0).Verification
just docs-build --strictclean;just check-planningOK;node --checkclean.verify-demos(retry tour completes on the single blip scenario),verify-herd,verify-real-page.🤖 Generated with Claude Code