Cycle Review

After Phase 2 completes, you MUST stop and present the user with a concise summary:

1. Goal — what we're solving (from Strategist)
2. Key findings — relevant facts, constraints, or conflicts discovered
3. Plan — what will be built, which files will be created/modified, interfaces defined (from Architect)
4. Risks — any alpha/chi interference or unresolved structural conflicts

Then ask the user explicitly: "Proceed with implementation, adjust the plan, or stop?"

Do NOT continue to Phase 3 until the user confirms.

Phase 3: Implementation (Implementer)

Only after user approval. Use the Implementer agent with the Architect's plan to:

• Complete the tau-checkpoint (plan exists, interfaces known, integration points clear, error handling defined)
• Write and integrate the code (phi x tau)
• Report any technical constraints discovered (phi => chi)

Phase 4: Verification (Evolution)

Use the Evolution agent to:

• Run tests and verify the implementation (omega recursive)
• Check harmony with original purpose (omega ~ alpha)
• Identify any change pressure (delta-psi) for future iterations
• Report results and recommendations

After all phases, summarize the cycle results and any remaining delta-psi (change pressure) for the next iteration.