The suite follows record presentations through its customer outcomes, lifecycle actions, permission refusals and retained regression cases. Each scenario names the capabilities it exercises and the detailed outcomes it relies on. Existing executable bindings identify specific assertions, while unbound scenarios remain proposed acceptance work.
Object archival changes form consumption and record availability. The interaction case checks the joint outcome after configuration or record state changes, so separate capability checks cannot stand in for the complete feature result. Presentation management is one capability; its feature interaction therefore crosses to object lifecycle and record consumption.