This is neat! There's definitely a missing formal, human layer sitting above code. Two thoughts come to mind:
1. For applications with a database, the database schema for core models strikes me as the canonical definition, except it's missing descriptions.
2. It feels like this is only a partial solution. Why not go all the way? It seems to me that more aspects of code needs this level of governance than just data models.
1. For applications with a database, the database schema for core models strikes me as the canonical definition, except it's missing descriptions. 2. It feels like this is only a partial solution. Why not go all the way? It seems to me that more aspects of code needs this level of governance than just data models.