canon-inspect-clarity

To check requirements for missing context before a governed run, inspect authored inputs using a clarity tool to surface targeted clarification questions and generate a concise clarity report without creating run artifacts.

A pre-run clarity inspection analyzes authored requirements or discovery inputs to identify missing context, applying canonical input surfaces to generate targeted clarification questions prior to run start.

To generate clarification questions from discovery inputs, run a clarity inspection in discovery mode to reason over current inputs and surface Canon-backed clarifications for a well-scoped run.

Yes, you can inspect discovery inputs without creating run state or artifacts because the pre-run clarity inspection only produces a clarity report and top questions without executing the actual governed run.

Yes, pre-run inspection supports both requirements and discovery modes by taking canonical input surfaces from either mode to generate targeted clarification questions before starting a governed run.