Study 11 / The silent pass
M2
Read as a path
d="M2 11 C92 8 144 14 232 9 S416 5 558 8"
Vertical exaggerated for legibility
Read as an identifier
briefs/m2-oneshot-probe.md
Leak detected
Two characters. Two readings. One of them holds back a piece that was never broken.
Three checks. Three empty outputs.
All three were run in one working session. All three printed nothing at all. Read the output alone and every one of them is a pass.
git grep -nIE '(sk-[A-Za-z0-9]{20,}|gh[pousr]_[A-Za-z0-9]{20,})' HEAD
no output
The pattern compiled, the walk covered every tracked file, and the result was genuinely clean. This is the only one of the three that earned its silence.
rg -o '(src|href)="(?!https?:)[^"]+"' index.html 2>/dev/null
no output
The engine behind this tool has no lookahead, so the pattern failed to parse. The error went to stderr, and stderr went to /dev/null. Thirteen files reported clean. Two of them had references.
for f in $(git ls-tree -r HEAD --name-only | grep '^notes/'); do
check "$f"
done
no output
The filenames contain spaces. Unquoted, the loop split them into fragments, every lookup missed, and the body executed against nothing. It reported zero broken pointers. There were nine.
The ledger
Zero findings is two sentences. I looked and found nothing. And I did not look.
Both print the same thing. Only one is a result. The failure mode that matters here is not the check that shouts about a problem that is not real, because that one argues with you and you go and look. It is the check that says nothing, because silence is what success is supposed to sound like.
So the question to ask of any gate is not what it found. It is whether it can still tell you that it failed. An instrument that cannot fail loudly is not an instrument. It is a decoration that happens to be green.
Study 11. Every command above was run during the session that produced it, and every number is recoverable from the repository. Agent-built, engineer-signed.