Repository navigation
docs(adr): say where ADR-0010's wrong fact actually came from - #295
Merged
Merged
Conversation
The verification section merged in #285 opened by saying the Context was written from Lemmiwinks pages "which #123 flagged as nine months stale, self-inconsistent and unchecked". That reads as though the error lived in the vault. It did not, and the dates say so. This ADR was added 2026-08-24, and on that date the vault did say external DNS was Cloudflare and Google -- the claim was copied accurately. Six days later, on 2026-08-30, the vault settled that section against /cf/conf/config.xml and corrected itself twice in one day: dhcp_dns_architecture now answers "there isn't one, and that is the correct answer rather than a gap", and dns_is_broken's source note carries a standing instruction not to restore the forwarding description. Both landed eleven days before the verification section claimed they were stale. So the wiki repaired itself in six days and this ADR carried the superseded claim for eleven more. #123, filed the same day as the ADR, quotes that same superseded text and reasons from it that the vault is nine months stale -- which is how one stale copy becomes an argument about the source it was copied from. The lesson is worth more than the correction: a copied fact goes stale at the copy, and the copy is the one with nobody watching it. No measured fact changes. Both findings, the recursive resolver and the static-mapping exception, stand exactly as verified. Refs #123 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 4, 2026
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.
#285's verification section opened by saying the Context was written from Lemmiwinks pages "which #123 flagged as nine months stale, self-inconsistent and unchecked." That reads as though the error lived in the vault. It did not.
The dates
/cf/conf/config.xmland corrects itself twice in one day:network/dhcp_dns_architectureanswers "There isn't one, and that is the correct answer rather than a gap", andrunbooks/dns_is_broken's source note carries a standing instruction not to restore the forwarding description.morpheus, finds the ADR wrong — and describes the vault as the stale party. Both corrections were eleven days old.So the wiki repaired itself in six days, and this ADR carried the superseded claim for eleven more. #123, filed the same day as the ADR, quotes that same superseded text and reasons from it that the Lemmiwinks pages are nine months stale — which is how one stale copy turns into an argument about the source it was copied from.
What this changes
The paragraph now says where the error came from and draws the lesson that is actually available: a copied fact goes stale at the copy, and the copy is the one with nobody watching it.
No measured fact changes. Both findings stand exactly as verified on 2026-09-04 — Unbound is recursive with zero
forward-zoneblocks, andMekenna-Laptopis handed8.8.8.8/9.9.9.9by static mapping. The correction banner at the top of the ADR is untouched, and so is everything under it.Docs only;
make lintpasses. The vault side of this is Gerrrt/Lemmiwinks#169.Refs #123
🤖 Generated with Claude Code