Transit must record which division owns each platform package for audits. What modeling approach fits?
Select an answer to reveal the explanation.
Short Explanation
Ownership for audits is metadata—author the division in custom metadata on the package. Do not hide it in mesh names or paint hues. Auditors read fields, not rainbows.
Full Explanation
Transit division ownership for audits is governance metadata and should be authored in custom metadata on the platform package prims or layers. Auditors and asset managers need a stable field that survives renaming, retargeting, and shading changes. Custom metadata keeps ownership queryable without abusing display or naming conventions that break under normal library hygiene.
Renaming every mesh after the division manager couples ownership to display names, collides with unique naming rules, and fails when managers change. Encoding ownership only in random prim name hashes is opaque and unverifiable. Storing ownership exclusively as displayColor hue misuses visualization channels and cannot represent organizational identity reliably under different color-management pipelines.
Exam caveat: define a controlled vocabulary for division names/codes in customData so spellings do not drift. Ownership metadata complements—not replaces—file ACLs and repository permissions.
Operational check: stamp division ownership in custom metadata on a platform package, run an audit report that lists ownership by prim, recolor materials and rename meshes to prove ownership fields remain, and gate CI on presence of the ownership key before publish.