Favoring Composition over Inheritence
Heeding the warning, removing db:test:prepare

Rails was indicating that db:test:prepare is going to be deprecated.
Ensuring validator is included
Adding explicit #validate method

In switching from inheritence to composition, I encountered the
a delegator problem.

The point of entry for validation is the Validator#validate method;
this is true of Rails and true of Hydramata::Works::ValidationService.

What is happening prior to this commit is that we have the Validation
object and its collaborating BaseValidator. When the application
attempts to call Validation#validate, the delegator passing along the
behavior to the BaseValidator#validate and the #validate_each message
is received by the BaseValidator instance, and thus uses the initial
behavior.

So in favoring composition, I encountered a problem resolved by
inheritance.
Partially completing end to end attachment

Attachments are a different critter than other predicates. By the
nature of processing HTML form input the file based predicates are
different.

In the case of other input types (i.e. text, date, integer), those
input fields are passed along the request as plain text. They are a
"simple" data type.

Contrast with the file input type; The data sent is a "complex"
data type. One that requires reading the input buffer, writing it to
another location, and persisting it somewhere that might be very
different from where other predicats can be persisted.