A model-driven view summarizes a population of records using selected columns and a filter. A form supports reading or changing one record. The two surfaces can share a source without needing identical layouts. A compact queue should preserve enough identity to select the correct request.
The browser model executes its saved views against fictional data and exposes their definitions. Check both the returned population and the requested columns. Removing a field from a view does not revoke a data permission, and hiding a required card does not erase its source constraint. These exercises include approval and priority populations, then ask you to distinguish layout decisions from validation and effective access.