Adding a stubbed method
Adding submit_ingest_etd
Removing callbacks

Prefer instead the explicit
Adding details concerning not advancing state

In some cases the state machine will be advanced by machine, in other
cases the advancement must happen by a user.

In the case of the after_trigger_ingest, there is an asynchronous
job that will need to trigger an event after it is complete.
Passing user along to advance a trigger
Adding a functioning Repository#log_event! method
Renaming method for greater specificity
Exposing module functions for the repository

The idea is that I want to make private constaints that I can use
within the context of the Repository, but not outside. These
constaints will allow me to make use of support methods without
requiring a second layer of modules and labrythine includes.
Teasing out notification methods
Renaming module Repo to RepositoryMethods

I'm interested in privatizing, as a good capitalist, all of the
underlying RepositoryMethod constants. The reason being that I want
to start crafting support module functions that are usable within the
Repository but not outside.

I believe this highlights a possible code smell, but for now I'm
willing to live with that as I'm hoping to isolate the stink to the
Repository class.

It is also possible that I'm going to need to create multiple
repositories at a future point. That would be the likely refactoring.
Merge branch 'refactoring-repository-constants'

* refactoring-repository-constants:
  Renaming module Repo to RepositoryMethods
Privating classes
Replacing constant reference with module function
Adding nodoc imperative for repository methods
Merge branch 'privatizing-repository-methods'

* privatizing-repository-methods:
  Adding nodoc imperative for repository methods
  Replacing constant reference with module function
  Privating classes
Adding AdditionalAttributeMethods
Moving methods to AdditionalAttributeMethods
Adding a TODO not about command/query separation
Factoring away deprecated methods

I'm in an ongoing pursuit to tease apart the repository. My
understanding of the repository concept is improving. This is amongst
the first steps.

Further plans are to separate commands and queries. Queries can be
public modules that decorators and so on can include.

This is my ongoing effort to avoid over-reliance on Rails. I can treat
it as a Repository layer, but I don't want to do that (yet).
Merge branch 'refactoring'

* refactoring:
  Factoring away deprecated methods