Hey @andrewhr, just saw your message. Chimera will roll up entity type definitions by inspecting the sequence of migrations and using that to build a point-in-time entity type model. Chimera/Arachne will never inspect a database (except to assert that what is present matches what is expected); the configuration is always the source of truth.

@luke yeah, looks like a sane tradeoff to me. Native migrations should really be the exception (and preferably, only at application-level modules)

thanks for the response!