Propose Analytical Scope

When: After you have inspected the model and its underlying data. You have read the package's sources and fields and looked at the data distributions.

Tool names are written bare here - get_context, execute_query, search_malloy_docs. The exact prefixed name depends on the host surface; match each against the tools you actually have.

Goal: Present what you found and recommend an analytical focus. The user selects a direction.

Ground yourself first with get_context: it returns the package's sources, views, and fields, so it tells you what data exists, how it relates, and what is already modeled. Query the data with execute_query to get row counts and spot data-quality issues. Record the proposal and the user's decision in your modeling workflow's modeling-notes.md.

Scope is "which questions", not just "which tables". A single A/B/C question about table inclusion is step 3's architecture question wearing step 2's clothes. The scope proposal must establish what the model is for: a model aimed at recommendation looks different from one aimed at catalog analysis over the same tables.

What to Present

1. Table Summary

Present a table of the discovered tables with key metadata: