Appendix A: The Field Card

Not a module — a standalone quick-reference, meant to be visible during an actual call, not read as instruction.

STEP 0 — Who's talking? What's their standing on this topic?

THE LADDER (stop at first yes)
  Would this be true no matter what system is used?        → L0
  Could this be diagrammed with no system named?            → L1
  Would two engineers agree on scope from this alone?       → L2
  Would this need no further client input to resolve?       → L3

THE RULE
  No L3 question until an L2 bridge exists for this thread.
  No topic closes at L0/L1 without attempting a bridge.
  No bridge before there's enough L0/L1 to justify it.

THE BRIDGE
  "It sounds like [system] needs to [capability] — right?"
  (name whose position it synthesizes if >1 stakeholder)

THE THREE TELLS
  Spelunking — 5 min on a mechanic, can't state the requirement it serves
  Blindness  — feels great, no sentence you constructed
  Overuse    — answers getting shorter, no corrections coming back

BEFORE TRUSTING A CONFIRMED L2, ASK
  Does it actually achieve the L0? Or just treat a symptom?