I spent the whole night reviewing the experimental report of wanman ai, cycling from 50 working days to 200 working days. I’ll share some reports with everyone, and in the meantime, I am almost certain that I won’t need to personally vibe and write any code next month. Goal: To create a software company focused on serving automotive users in the Japanese market. Time spent: 50 minutes (200 loops) Model: CEO + CTO = Claude Opus 4.6 / Workers = Qwen 3.5 35B model Key contributions of the CTO Agent (Opus) Lifecycle: 3 activations (Loop 68-85, 100-122, 148-196) 1. v1.0 architecture spec (Loop 82-83): Complete product definition + technical architecture, 1175 lines, 54KB 2. LINE Mini App evaluation (Loop 120): After the CEO proposed the H3 hypothesis, the CTO completed a 25KB feasibility assessment 3. v2.0 architecture update (Loop 192): Changed the entire architecture to "LINE Mini App First" based on the evaluation results ... The CEO entered the divergence phase in Loop 99, generating 3 hypotheses: 1. H1: Deep vertical cultivation of vehicle inspection scenarios — Using Japan's unique vehicle inspection system as a PMF entry point 2. H2: B2B2C model — Collaborating with 90,000 maintenance shops for low-cost customer acquisition 3. H3: LINE Mini App — Utilizing LINE's 95 million MAU to replace independent apps ← Verified and adopted by the CTO! After Loop 84 started, actual code was produced in E2E Tasks stagnated after Loop 175 Between Loop 175 and 200, the number of completed tasks remained at 9/16, with 7 assigned tasks showing no progress. The main issues were: - MVP development tasks for dev (blocked on architecture update) - Architecture update tasks for the CTO (Loop 148-196 in progress but not marked as complete) - Second-phase correction tasks for finance/devops/feedback/marketing.