Run the routing probe on every deploy, which is what makes it a guard - #268
Merged
Merged
Conversation
T005c. Wired into ~/update-beta-chat.sh beside the sweep, honouring the same --skip-sweep flag. One run of the probe is a measurement; the risk it addresses is drift, so only repetition makes it a control. A classifier that stops choosing a collection next month would otherwise give confident answers and a green sweep. It fails the deploy and points at --rollback rather than rolling back itself -- the judgement the sweep already makes, since a rollback is disruptive and the container is already serving. An image built before the probe existed skips it with a warning, so the check cannot block a rollback to an older tag; verified against the running container, which is exactly that case today. That script is not version controlled, so this task is its only record here. Co-Authored-By: Claude Opus 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.
T005c. The probe from #267 is wired into
~/update-beta-chat.sh, immediately after the sweep and honouring the same--skip-sweepflag.One run of a probe is a measurement. The risk it addresses is drift — a classifier that stops choosing
complexesnext month gives confident answers and a green sweep — so only repetition turns it into a control. That is the whole point of this change, and it is why #267 on its own did not close the risk.It fails the deploy and points at
--rollbackrather than rolling back by itself: the same judgement the sweep already makes, since a rollback is disruptive too, the container is already serving, and which is worse depends on the failure.An image built before the probe existed skips it with a warning rather than failing, so the check cannot block a rollback to an older tag. Verified against the running container, which is exactly that case today —
bin/answer-sweepis present andbin/routing-probeis not, so the guard is discriminating rather than always-true.The script is not version controlled, so this task is its only record in the repository. Backed up before editing and
bash -nclean.Documentation only here; the script change is outside the repo.
🤖 Generated with Claude Code