CONCEPT · ABSENCE ISN’T A GAP
“There’s no auth layer here. Is that a hole?”
The same absence, three verdicts.
One fact — no auth layer in this file— lands three different ways depending on stance. Stance is just Preston’s read of who’s responsible for the absence — and, as you’ll see, a read you can argue with. Only one of the three is a defect.
A tool that greps for an “auth layer” and doesn’t find a file by that name will happily report a hole — even when auth is handled cleanly one layer up, or handed off on purpose to whoever calls this library. The absence is real; the alarm is wrong. So Preston treats an absence as a question rather than a conclusion, and only one of the three answers is worth your attention.
Red is the only flag. The other two are Preston telling you the quiet is earned.
And a stance isn’t a verdict handed down. It is a belief about who owns the absence, and a belief is something you can argue with: if Preston reads one as missing when you meant it as handled, you say so, and both readings stay live until something settles it.
challenge records your disagreement with a stance — additive, and it never deletes what Preston believed. The disagreement stands beside the belief, in the open, with your reason attached.
RELATED
What it won’t say →