Hardware
The datasheet outranks memory
The model has read a thousand datasheets; yours is rev B. Feed it the document, then make it derive.
The machine has read a thousand datasheets, which is precisely the danger: for any famous part it carries a confident prior, and your board carries a revision. The sixth law's bench form is absolute. Feed it the actual document for the actual part, and make every register, coefficient, and timing derive from that document, not from the family resemblance it remembers. Plausible-and-nearby is the failure mode that solders.
The same prior contaminates physics itself. A remembered rule of thumb arrives with the same confidence as a measured fact, and hardware does not forgive the difference. When a claimed limit smells wrong, and especially when it conveniently ends the discussion, send it back to the literature before designing around it.
How to practice it
The revision outranks the family.
Rev B is not rev A with a suffix. Work from the exact document for the exact part in your BOM, attached, not remembered.
Make it derive.
Constants come with a citation to the page and table they came from. A register map without provenance is a guess in a grid.
Interrogate remembered physics.
Rules of thumb are hypotheses wearing lab coats. If a claimed limit shapes your design, verify it in sources first.
Nearby is wrong.
Adjacent addresses, sibling parts, last generation's calibration: each fits perfectly and fails electrically.
Deep scripture: Codeuteronomy VII — The source is authoritative; the agent's guess is not