01 THINKHow does he reason?

A check that never fails is not a check

Every guard gets deliberately broken. A guard confirmed only by passing guarantees nothing.

I built the contrast guard and it passed immediately. Green light.

But one green light cannot tell two things apart.

Guard passesThe values are correctIt checks nothing at allBoth branches emit the same signal. So it gets broken on purpose, every time.
# Threshold violation
sed -i '' "s/--muted: #70706e;/--muted: #b0b0ae;/" styles/tokens.css
node scripts/check-contrast.mjs   # must exit 1

# Drift from the published figures
sed -i '' "s/--muted: #70706e;/--muted: #5f5f5d;/" styles/tokens.css
node scripts/check-contrast.mjs   # valid value, disagrees with the docs -> exit 1

The point is that the two failure modes are different. The first is accessibility broken; the second is accessibility fine, documentation lying. A design system that shows visitors its numbers has to know the moment those numbers stop being true.

The cascade-layer guard was verified the same way. Putting a module back inside a layer and building caught it exactly.

testingtooling

Record

First committed 2026.08.24, and changed 2 times since.

  • 9cf738eContent: 어려운 대목 넷을 그림으로 바꿨다
  • 029cadaTopics: a controlled axis to browse by, and a filter that costs no JavaScript
  • 8987da1Phase 2: Personal System

The full build record →