Parks staff see a pavilion roof opinion from a payload lose to a stronger reference opinion. What LIVERPS implication explains that?
Select an answer to reveal the explanation.
Short Explanation
On the LIVERPS ladder, References sit above Payload—so a referenced roof opinion can beat a payload opinion. That’s expected strength, not a mystery bug.
Full Explanation
LIVERPS places References stronger than Payload. When parks staff see a pavilion roof opinion from a payload lose to a stronger reference opinion, the correct implication is that in LIVERPS, References are stronger than Payload, so the reference roof opinion can outrank the payload. That outcome is expected composition strength—not a renderer bug—and guides how parks should structure pavilion assemblies that mix referenced shells with deferred payload detail.
Claiming payloads are always strongest so the result must be a renderer bug fails by concept: Payload is weaker than Local/Inherits/Variants/References; losing to a reference is correct. Claiming Payload and Reference strengths are identical and that layer filename length decides fails because References outrank Payload, and filename length is not a strength metric. Claiming Specializes always outranks both References and Payload for roof attributes fails because Specializes is the weakest LIVERPS rung, not the strongest.
Exam caveat: References > Payload; Specializes is weakest; filename length is irrelevant to LIVERPS arc order. Operational check: compose a pavilion with a reference roof opinion and a conflicting payload roof opinion, confirm the reference wins, document the winning arc for the parks team, and only then decide whether a Local override is needed for a site-specific civic roof correction.