rea-analysis-optimization

Topics in the source

• REA analysis optimization
• Pin the question and the correctness oracle
• Locate the earliest unnecessary work
• Keep one interpretation and a defined reuse lifetime
• Compare completed tasks and limit the claim

Find a concrete source of unnecessary work, change it at its owner, and verify equivalent completed investigations. A useful outcome can also be a measured decision to leave an implementation alone. Follow the checkout's performance priorities, tool design, and testing guide. This skill supplies an optimization workflow, not additional permission to execute targets, publish, or merge. Use the current contracts, provider prerequisites, and user authorization. Reserve performance measurements for changes that target performance or have a concrete regression concern. Routine cleanup uses correctness checks and does not require this optimization workflow or synthetic benchmarks merely because helper calls, imports, or representations change. Read the Kuna case study when selecting a reuse strategy or interpreting a benchmark. Its pinned observations illustrate tradeoffs; they are not current-provider guarantees or universal speedups. Describe the analyst's completed task, including the facts and relationships needed to answer it, requested detail, source access, and meaningful unknowns. Choose a representative real artifact and a small or empty case. Record the baseline revision, targe

This is an excerpt. Refer to the complete source and its current requirements.