distill — Grounded Intent Inquiry

Domain Rubric

Intent Boundaries

• Separate desired outcome X from requested mechanism Y. Extract independently assessable intents with stable IDs (I1, I2, ...); shared goals or mechanisms are valid.
• Preserve explicit requests and label inferred intent as inferred. An outcome without a mechanism is valid; keep its solution open rather than inventing technologies.
• Ground proposals with targeted authoritative docs and relevant code. Inspect enough to identify context and boundaries; reserve suitability evaluation for confirmed intent.
• User confirmation establishes intended meaning, not runtime proof or implementation authorization. Preserve confirmed context across turns; revisions invalidate only affected intents and their dependent claims.
• Keep inquiry read-only: inspect and report; leave design, workspace mutation, and experiments to separately invoked workflows.

Post-Confirmation Evaluation

Assess each confirmed intent against: