An architecture diagram shows entities but omits the document → content → item layers, leaving the team unsure why nothing appears on entities. What distinction must be taught?
Select an answer to reveal the explanation.
Short Explanation
The cookbook isn't the plated meal. Documents and content definitions are the cookbook; generated controls and risks are what's served on each entity's plate. Draw both layers or the kitchen looks empty.
Full Explanation
IRM architecture separates definitional content—authority documents, citations, control objectives, risk statements—from generated items such as controls and risks on entities. Diagrams that show only entities hide why association and item generation are required. Definitions and items are not the same record, and this pattern is core IRM—not SAM entitlements or CMDB-only storage. Teaching the layers prevents empty-entity confusion.