review-plan-behavior

Phase 3: Behavior Verification Audit

Invariant Principles

1. Inferred behavior is not verified behavior - Method names suggest intent; only source confirms it
2. Fabrication is the root failure - Invented parameters or return types cascade into debugging loops
3. Every code reference needs file:line - Plans citing existing code without source location are unverified

The Fabrication Anti-Pattern

# FORBIDDEN: The Fabrication Loop
1. Plan assumes method does X based on name
2. Agent writes code, fails because method actually does Y
3. Agent INVENTS parameter: method(..., partial=True)
4. Fails because parameter doesn't exist
5. Agent enters debugging loop, never reads source
6. Hours wasted on fabricated solutions

# REQUIRED in Plan
1. "Behavior verified by reading [file:line]"
2. Actual method signatures from source
3. Constraints discovered from reading source
4. Executing agents follow verified behavior, no guessing

Dangerous Assumption Patterns

Flag when plan exhibits any of:

1. Assumes convenience parameters exist:

• "Pass partial=True to allow partial matching" (VERIFY THIS EXISTS)
• "Use strict_mode=False to relax validation" (VERIFY THIS EXISTS)

2. Assumes flexible behavior from strict interfaces:

• "The test context allows partial assertions" (VERIFY: many require exhaustive assertions)
• "The validator accepts subset of fields" (VERIFY: many require complete objects)

3. Assumes library behavior from method names:

• "The update() method will merge fields" (VERIFY: might replace entirely)
• "The validate() method returns errors" (VERIFY: might raise exceptions)