grill-melisted

# Grill Me Interview the user relentlessly about every aspect of an Odoo plan until there is shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. Ask exactly one question at a time. For each question, include your recommended answer. If a question can be answered by exploring the codebase, inspect the codebase instead of asking. ## First Move Before asking, gather discoverable facts: - Odoo version and edition if visible from branch/docs/config. - Addon/module names and manifests. - Existing models, views, security, data, controllers, assets, tests, and docs relevant to the plan. - `$ODOO_SOURCE`, `$ODOO_TOOL_README`, and `$ODOO_BASE_COMMAND` context when available. Then ask the highest-leverage unresolved question. ## Question Branches Use only the branches relevant to the plan. ### Product And Workflow - What user workflow is being changed? - Which users/groups need it? - What should happen in draft, confirmed, cancelled, archived, or error states? - What business invariant must never be violated? ### Module Boundary - Which addon owns the concept? - Is this a new addon, extension of an existing addon, or configuration/data-only change? - Which manifest dependencies are real, and which would be convenience dependencies? - Does the plan couple unrelated business domains? ### Model Design - Is this a new model, `_inherit`, or `_inherits`? - What is the lifecycle of the record? - Which fields are st