Anyway, it might make sense in the future to wrap raw assertion objects in a class with some methods. The `Badge` model is really for storing metadata about the assertion. It might make sense to have an `Assertion` model, even if it's a model that's not represented in the database (though having it in the DB might be okay – we could do a foreign key relationship to the `assertion` table, then hang indexes-as-columns for anything in the JSON blob that we need quick access to).

I don't think we should try to do that with this pull request though.