You make an excellent point, and it's important to understand that these higher-level templates need not be static, immutable, canonical representations of instances of classes but rather models informing when and how its parts should be presented.

I think the same question applies to lower-level UI components. Don't primitive fields also rely on their context to properly behave and present themselves? For example, text is rendered differently based on language, location, screen size, accessibility settings, and time of day. Likewise, text fields behave differently whether they represent a person's name, an email address, a phone number, a credit card number, or a password.

Similarly, a person template should also adapt to its context and the intent of the user to properly select an appropriate presentation. For example, if a list of authors is filtered to only show American authors, then it might not make sense for item templates to redundantly show the author's nationality. Whether this task can be sufficiently automated to be practical without AGI is still an open question which I'm attempting to resolve.