The workshop pilot needs several compact queues and a clear explanation of its model constraints. Start from each requested population and decide which fields support selection. A correct count on the wrong source or a view missing its identity column is not a complete handoff.
These tasks combine earlier view actions and individual modeling decisions on fresh data. Keep source requirements separate from visible layouts and data permissions. When a relationship is unknown, preserve that absence instead of inventing a parent. The executable local views provide concrete evidence, while the reasoning tasks state what a real Dataverse implementation would still require. No tenant metadata changes are implied.