Rapid Convergence

Rapid convergence uses a structured assessment of 5 key criteria—baseline metrics, domain focus, validation directness, prior art, and success criteria clarity—to identify when you can achieve methodology convergence in 3-4 iterations instead of the standard 5-7. Score 4-5 YES answers to unlock this acceleration.

Use rapid convergence when you have a clear baseline to measure against, your domain is focused and well-defined, direct retrospective validation is feasible, and success criteria are established. Apply it at project kickoff to assess realistic iteration timelines and set accurate delivery expectations.

Rapid convergence compresses methodology development from 5-7 iterations (20-30 hours) into 3-4 iterations (10-15 hours) by optimizing for clarity and direct validation. Standard development suits exploratory work; rapid convergence requires established baselines and focused domains for measurable 40-60% time savings.

No. Rapid convergence requires a clear V_meta baseline to function. If baseline metrics don't exist, establish them first through exploratory work, then apply rapid convergence once you have measurable starting points and validated success criteria.

Rapid convergence includes a retrospective validation phase that measures outcomes against documented patterns and tools. Use generic agents to execute experiments, then validate results directly against your success criteria to confirm 3-4 iteration convergence within 10-15 hours.

If your domain assessment scores 0-1 YES criteria, expect exploratory iteration (6-10 iterations) and establish baseline metrics first. Rapid convergence applies only when domain boundaries are clear, prior art exists, and validation pathways are direct—not in discovery phases.