Governance DNA

DNA is the right metaphor because of inheritance. When ownership, classification, retention, and quality expectations are properties of the model — attached to the concept, the attribute, the mapping — every artifact generated from that model carries them automatically. Tag an attribute as personal data once, and every generated table, view, test, and documentation page downstream expresses that classification, because they were all synthesized from the same genome. Contrast this with bolt-on governance: a catalog team annotating artifacts after they exist, forever chasing a platform that changes faster than they can tag it. In the DNA model there is nothing to chase — an artifact cannot exist without its governance traits, because generation is the only way artifacts come into being. Coverage is 100% by construction, not by campaign. Within the governance cluster, Governance DNA names where the encoding lives: in the model, upstream of everything. Embedded governance describes the enforcement happening inside the platform flow, and governance-as-code describes the engineering form of the layer as a whole — DNA is the inheritance mechanism underneath both.