Why does a typo in a derived query method's field name fail at startup rather than at call time?

Spring Data parses and validates a derived method's name against the entity's actual mapped fields eagerly, when it builds the repository proxy at application startup — not lazily, on first invocation — so a field that doesn't exist is caught immediately rather than causing a runtime failure later.