With respect, I disagree in this case. My primary motivation in this branch was to take methods that were doing way to much, separate out logic, keep each step nice and functional, with one composing method that, thanks to the separation, reads like a description of the use case procedure. I don't see the advantage of cramming these otherwise unrelated lines of logic into one method. I'm not sure if the short methods need to make sense outside the context of the "make ineligible" use case. Is it not good enough that their functionality in concisely summed-up in their names?