Here's the thing: Commit edf8e1c basically completes the use case but, in doing so, we now have a new class defined in our tests that looks like it "ought" to be at least the basis of a new Article value object, likely (eventually) replacing Prolog::Core::Article.
This issue is a reminder to break out that value object/entity, and to rethink Prolog::Core::Article.
Marked as a feature rather than an enhancement or a bug fix because one could easily argue that it's any of the three, and "feature" carries somewhat more urgency than "enhancement" (which we feel is appropriate here) without the negative connotations of "bug" (which we're not quite sure applies here).
Quoting a comment on Issue #37:
This issue is a reminder to break out that value object/entity, and to rethink
Prolog::Core::Article.Marked as a feature rather than an enhancement or a bug fix because one could easily argue that it's any of the three, and "feature" carries somewhat more urgency than "enhancement" (which we feel is appropriate here) without the negative connotations of "bug" (which we're not quite sure applies here).