Two sentences the step-2 rewrite left pointing at the old gate - #107
Merged
Conversation
#105 moved this doc to marketdata-update and corrected the --require-final paragraph itself, but two supporting sentences elsewhere in the file still describe the wall-clock mechanism that was replaced. The restart-on-failure paragraph told the reader each retry is a last_database_update_time check. That is the dead mechanism, named in the one paragraph whose whole job is explaining why the retry loop is cheap enough to run every ten minutes. It is now what actually happens: a short trailing-window read and a date compare. The testing section said a daytime run only proves the wrapper resolves. That was true of a clock gate, which could not be satisfied before evening no matter what the store held. Under a date comparison it is conditional, and the condition is worth stating because it is an operational property rather than a detail: a daytime run defers only if last night captured. If last night failed or never fired, Norgate is ahead of the store and the daytime run captures immediately, so a missed night self-heals at the next trigger instead of waiting another evening. The old wording told an operator the opposite of that. Docs only, no code touched. 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.
Follow-up to #105, and the salvage from #106 which I closed as superseded.
#105 moved this doc to
marketdata-updateand corrected the--require-finalparagraph itself. Two supporting sentences elsewhere in the file still describe the wall-clock mechanism that was replaced.The restart-on-failure paragraph told the reader each retry is a
last_database_update_timecheck. That is the dead mechanism, named in the one paragraph whose whole job is explaining why the retry loop is cheap enough to run every ten minutes. It now says what actually happens: a short trailing-window read and a date compare.The testing section said a daytime run only proves the wrapper resolves. That was true of a clock gate, which could not be satisfied before evening no matter what the store held. Under a date comparison it is conditional, and the condition is worth stating because it is operational rather than trivia: a daytime run defers only if last night captured. If last night failed or never fired, Norgate is ahead of the store and the daytime run captures immediately, so a missed night self-heals at the next trigger instead of waiting another evening. The old wording told an operator the opposite.
Docs only, no code touched.
🤖 Generated with Claude Code