reflection

**Reflection** is **a post-attempt review method where the model critiques failures and generates corrective guidance for retries** - It is a core method in modern LLM workflow execution. **What Is Reflection?** - **Definition**: a post-attempt review method where the model critiques failures and generates corrective guidance for retries. - **Core Mechanism**: After an initial attempt, a reflector stage identifies mistakes and proposes improved strategies or constraints. - **Operational Scope**: It is applied in LLM application engineering and production orchestration workflows to improve reliability, controllability, and measurable output quality. - **Failure Modes**: Superficial reflections can add verbosity without fixing root causes in subsequent attempts. **Why Reflection Matters** - **Outcome Quality**: Better methods improve decision reliability, efficiency, and measurable impact. - **Risk Management**: Structured controls reduce instability, bias loops, and hidden failure modes. - **Operational Efficiency**: Well-calibrated methods lower rework and accelerate learning cycles. - **Strategic Alignment**: Clear metrics connect technical actions to business and sustainability goals. - **Scalable Deployment**: Robust approaches transfer effectively across domains and operating conditions. **How It Is Used in Practice** - **Method Selection**: Choose approaches by risk profile, implementation complexity, and measurable impact. - **Calibration**: Use targeted reflection prompts tied to objective error categories and measurable correction criteria. - **Validation**: Track objective metrics, compliance rates, and operational outcomes through recurring controlled reviews. Reflection is **a high-impact method for resilient LLM execution** - It improves iterative task success by turning failed attempts into actionable learning signals.