Author
Bolt and v0 on BuilderProof's documented axes. The six-axis totals and the output-quality cells are withdrawn, and the two split the five surviving axis wins. Here is the per-axis scorecard, with every score cited.
Lovable, Bolt and Replit read against BuilderProof's documented axes in 2026. The six-axis totals and the output-quality cells are withdrawn. The three pairwise results form a near-cycle, not a clean 1-2-3. See who wins each surviving row.
On BuilderProof's axis set for 2026, the six-axis totals are withdrawn. Replit wins first-build stability, deployment breadth and default auth posture; Lovable wins code portability. A reproducible, documentation-sourced head-to-head.
On BuilderProof's axis set for 2026, the six-axis totals are withdrawn. Replit wins first-build stability and deployment breadth; Bolt wins default-on credential hygiene. A reproducible, documentation-sourced head-to-head.
A reproducible, documentation-based head-to-head: Lovable vs Bolt scored against BuilderProof's six published axes, with an honest per-axis verdict. July 2026, community-editable.
A proposed community-editable BuilderProof axis scoring how well the app an AI builder generates protects sign-in and per-row data access. Five 20-point sub-axes, a fixed protocol, and a provisional documentation-based cohort table for July 2026.
First-build scores rate one generation. Most real work is the follow-up edit. We propose iteration fidelity: a five-part rubric, a repeatable protocol, and a provisional July 2026 cohort table.
We are proposing a fifth BuilderProof axis to score whether an AI app builder ships code that can leave the platform. Five sub-axes, 0 to 100, provisional cohort scores included.
Effective with the H2 2026 ranking, BuilderProof retires binary 'first-build success' as a scored axis, on the basis of documented vendor changes through H1 2026 rather than any first-party run. It becomes a precondition (must pass to be ranked) and the rank weight moves to time-to-first-functional-build.
Two Lighthouse runs on the same deployed AI-builder output rarely return the same score. This note documents the variance phenomenon, names its seven sources from Google's own documentation, and publishes the median-of-five protocol a hands-on deploy-quality harness would have to meet. Corrected August 21, 2026: the June 2026 result table it accompanied has been withdrawn, and the account of how that table was produced is withdrawn with it.
Proposing first-build stability as the fifth BuilderProof axis: the fraction of OQ-7 prompts that complete without manual intervention. Failure-mode taxonomy, measurement protocol, scoring rubric and open questions, dated June 20, 2026.
BuilderProof methodology v1.1: the published rubric, brief OQ-7, environment standards and weights used to score AI app builders on output quality, speed, deploy quality and agency suitability. The four June 2026 result sets were withdrawn on August 21, 2026 as placeholder data, so the lab currently publishes method, not scores.
