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

Spring Data validates a derived method name eagerly against the mapped @Document class's actual fields when it builds the repository proxy at startup — it isn't deferred until the method is actually called, so a field that doesn't exist on the entity is caught immediately rather than silently misbehaving later at runtime.