Now working for simple use cases is genericBelongsTo, though it will most likely not work in any client-side use case. (It depends on global.persist in several spots, as well as non-standard properties. Might be refactorable to included/exclude them, but not sure.)

Also, because of the current use of global persist, _persistance, and _static, this will likely not make sense or work until I fix/refactor in a way that brings in several code snippets that currently live in their own library.

I don't think there will be a genericHasMany. Similar functionality might be included in a joined related object fetcher/resolver.