A housing authority wants maintainable OpenUSD unit assemblies across campuses. What should structure guidelines define?
Select an answer to reveal the explanation.
Short Explanation
Housing twins scale when unit hierarchy and instance rules are on paper. One-off mesh dumps and chat-only rules will not survive the next campus.
Full Explanation
A housing authority wanting maintainable OpenUSD unit assemblies across campuses should define unit assembly hierarchy and instancing rules for reusable residential components. Hierarchy (building → unit type → interior kits) plus clear instance versus unique rules let campuses share kitchens, baths, and façades without unique mesh dumps per apartment. Documented structure is what keeps twins maintainable as campuses grow.
A requirement that each apartment is a unique non-reusable mesh dump fails by concept: unique dumps explode storage, defeat instancing, and make campus-wide fixes impossible. A ban on documenting hierarchy so authors invent trees per building fails because invented trees diverge and break automation. Guidance to store instance rules only in chat transcripts fails because chat is not durable pipeline policy and cannot gate CI.
Exam caveat: housing-scale USD succeeds with documented hierarchy/instancing, not one-off dumps or oral tradition. Operational check: write hierarchy and instancing standards, author a pilot unit assembly that instances shared kits, validate instance counts and paths across two campuses, and forbid chat-only instance policy in pipeline reviews.