Context. Vibe coding, building software by describing it to AI systems and accepting the code they write, now produces products that people pay for. Evidence comes mostly from interviews and online posts, rarely from the records of a live system built by a non-programmer. Objective. To describe how one such product was built and kept under control over its first 104 days, starting the day before public launch. Method. A single-case study of Curie, a research platform built by an environmental engineer who does not write code, using a commercial AI app builder and external AI agents. I analysed all 2,334 commits, 1,940 instructions to the builder, 2,457 checkpoints and weekly code snapshots. Results. AI tools generated every code change: the builder made 972 commits (41.6%) and external agents 1,296 (55.5%). Agent commits were smaller (median 21 against 87 lines; rank-biserial r = 0.40, p < 0.001); durability did not differ consistently once timing was controlled. Half of all file edits revisited a file changed within 24 hours. The codebase grew 6.2-fold while decision points per thousand lines rose 94%. Tests first appeared on day 88, and a rollback on day 102 discarded 302 commits, including half the tests. The product reached about 500 paying users. Conclusions. Ten guardrails, four prompted directly by platform behaviour, form a ladder from prototype to team: three observed levels and a proposed fourth. With AI writing all the code, the founder's work was directing the AI and checking its output.