bc-code-intelligence-mcp

# Execution Validation Phase - Real-Time Work Verification ## Overview **Objective**: Validate claimed optimizations actually exist in code through frequent, lightweight verification checks. **Key Principle**: Trust but verify - every optimization claim must be immediately validated against actual file contents. ## 🚨 FREQUENT MICRO-VALIDATION - RUNS CONTINUOUSLY **CRITICAL**: This phase runs multiple times per session, not once at the end. Prevents execution fraud through real-time validation. ### Execution Validation Triggers **MANDATORY VALIDATION POINTS** - Agent CANNOT proceed without validation: - After optimizing 2-3 files - When agent asks permission to continue - Before claiming any module "complete" - Before moving to next business domain - When agent pauses or requests guidance --- ## Phase Execution Process ### Step 1: Immediate Claim Validation **CRITICAL**: Validate optimization claims against actual file contents within minutes of claimed work. #### 🔍 Quick File Content Validation - [ ] **Verify Claimed CalcSums Optimizations** ```bash # REQUIRED: Validate CalcSums claims exist in files grep -l "CalcSums" file1.al file2.al file3.al # BLOCKING CONDITION: If claimed but grep returns empty = FRAUD ``` - [ ] **Verify Claimed SetLoadFields Optimizations** ```bash # REQUIRED: Validate SetLoadFields claims exist in files grep -l "SetLoadFields" file1.al file2.al file3.al # BLOCKING CONDITION: If claimed but grep returns empty = FRAUD ``` - [ ] **Verify Claimed Loop Eliminations** ```bash # REQUIRED: Check manual loops actually removed grep -c "repeat" file1.al file2.al # Should be reduced or zero grep -c "until.*Next" file1.al file2.al # Should be reduced or zero # BLOCKING CONDITION: If claimed eliminated but loops still exist = FALSE CLAIM ``` #### 🕐 File Modification Time Validation - [ ] **Verify Files Actually Modified** ```bash # REQUIRED: Check file modification timestamps ls -la --time-style=full-iso *.al | grep "$(date +%Y-%m-%d)" # BLOCKING CONDITION: Claimed optimization but file not modified today = FRAUD ``` ### Step 2: Optimization Pattern Verification **CRITICAL**: Ensure claimed patterns actually implemented correctly. #### 🔒 MANDATORY PATTERN CHECKS - [ ] **CalcSums Implementation Validation** ```bash # Verify proper CalcSums usage (not just presence) grep -A2 -B2 "CalcSums" file.al # Check: Proper field names, correct placement, no manual loops after ``` - [ ] **SetLoadFields Placement Validation** ```bash # Verify SetLoadFields placed before FindSet (BC best practice) grep -B1 -A1 "SetLoadFields" file.al # Check: Appears before FindSet/FindFirst, includes correct fields ``` - [ ] **Anti-Pattern Elimination Verification** ```bash # Ensure nested loops actually eliminated grep -C3 "repeat.*repeat" file.al # Should return empty for eliminated nested loops grep -C3 "FindSet.*FindSet" file.al # Should return empty for eliminated N+1 patterns ``` ### Step 3: Real-Time Fraud Detection **CRITICAL**: Immediately flag and stop execution fraud. #### 🚨 BLOCKING CONDITIONS (Session Stops Immediately) - **FALSE OPTIMIZATION CLAIMS**: Optimization claimed but not found in file - **PHANTOM FILE MODIFICATIONS**: Claims about files that weren't actually modified - **INCORRECT PATTERN IMPLEMENTATION**: Patterns exist but implemented incorrectly - **INCOMPLETE WORK**: Claims "all procedures optimized" but evidence shows partial work #### 🔧 FRAUD RESPONSE PROTOCOL When validation fails: 1. **STOP ALL WORK**: No further optimization work until resolved 2. **FORCE CORRECTION**: Agent must actually implement claimed optimization 3. **RE-VALIDATE**: Run validation again after claimed correction 4. **DOCUMENT FRAUD**: Log validation failure and correction in optimization log --- ## Validation Commands Reference ### File Content Validation ```bash # Validate specific optimization patterns exist grep -l "CalcSums" *.al grep -l "SetLoadFields" *.al grep -l "Count()" *.al grep -c "repeat" *.al # Should be reduced in optimized files # Validate anti-patterns eliminated grep -L "repeat.*until" *.al # Files with nested loops eliminated grep -c "FindSet" *.al # Should be optimized in aggregation files ``` ### File Modification Validation ```bash # Check files actually modified recently find . -name "*.al" -mtime -1 # Files modified in last day ls -lt *.al | head -5 # Most recently modified files # Compare modification times to optimization claims stat --format="%y %n" *.al # Detailed modification timestamps ``` ### Pattern Implementation Validation ```bash # Verify CalcSums implementation quality grep -A3 "CalcSums" *.al # Show context after CalcSums calls grep -B2 -A1 "SetLoadFields" *.al # Show SetLoadFields placement # Check for remaining anti-patterns grep -n "repeat" *.al | grep -v "CalcSums" # Manual loops not replaced with CalcSums ``` --- ## Success Criteria - ALL MUST PASS ✅ **File Modification Evidence**: All claimed files show recent modification timestamps ✅ **Pattern Presence Validation**: All claimed optimizations found in file contents ✅ **Implementation Quality**: Optimizations implemented according to best practices ✅ **Anti-Pattern Elimination**: Claimed eliminated patterns no longer present in code ✅ **No False Claims**: Zero discrepancies between claims and actual file contents ## Quality Validation Checklist - **Optimization Existence**: Can you grep for every claimed optimization? - **Implementation Correctness**: Are patterns implemented properly (SetLoadFields before FindSet, etc.)? - **File Modification**: Do file timestamps confirm recent changes? - **Anti-Pattern Removal**: Are claimed eliminated patterns actually gone? --- ## Execution Validation Workflow ### Trigger Points (MANDATORY) 1. **After 2-3 files optimized**: Run micro-validation 2. **Agent requests to continue**: BLOCK until validation passes 3. **Module completion claims**: VALIDATE before allowing progression 4. **Performance phase transitions**: VALIDATE all claimed work ### Validation Frequency - **Every 10-15 minutes** during active optimization work - **Before ANY completion claims** (module, phase, session) - **When agent asks permission** to proceed or continue - **After ANY substantial optimization claims** (CalcSums, SetLoadFields, etc.) ### Integration with Other Phases - **Performance Phase**: Execution validation runs during performance work - **Verification Phase**: Comprehensive validation runs after performance phase - **Analysis Phase**: Light validation can verify analysis claims were accurate --- ## Next Phase Upon successful execution validation, work can continue in Performance Phase. Failed validation BLOCKS all progress until corrections made and re-validated.