Summary
Coverage is explicit: missing and unevaluated cells display an em dash. They are not scores.
Treatments and runner readiness
Treatment scores
The primary value uses all 74 pinned plans. Available-case values are provisional and are not leaderboard scores.
24 × 4 result matrix
Per-app results
All 74 plan results
The wedding/test1 anomaly remains in the primary universe. The separate 73-plan value is an audit diagnostic only.
Per-cell records and construction files
Only exact file hashes in the checked-in reviewed-body allowlist can be fetched as inert JSON strings, and heuristic guards can still veto them. New or changed bodies are withheld by default. This is not a universal secret or PII detector. Candidate HTML and JavaScript are never loaded as documents or executed. Screenshots are not generated; raw private evidence is withheld.
Prompts and upstream inputs
Every cell receives the same canonical goal prompt plus its app's pinned MVP PRD and public assets. Test plans are evaluation inputs, not construction inputs.
Prompt SHA-256:
Methodology
Process
ViBench defines the tasks and scores. This project changes how agents build the apps. It does not replace ViBench. Each build agent builds the app through the product's native CLI or GUI and uses the product's native tools. The build agent does not receive the ViBench evaluator API key. The same fixed copy of the ViBench evaluator scores every treatment. The evaluator does not change with the build product. It uses its own API key. It does not build the app. We have not yet used the copied evaluator to score any of the 74 ViBench plans. In the first private test, the evaluator and the candidate app can run in the same container. This setup does not prove that the evaluator is isolated. We publish a comparable score only after the result passes all publication checks.
Scores
Upstream points anomaly
Missing cells
Public artifacts
Data
Download the normalized public data
data.json SHA-256: 05ee9e4966821c265331e583c41ee749a7410944d284e2992b54191dea8d33b3
artifact index SHA-256: 28bc23054eaac776db832675a8818ec332062f357c2122a3087b0fdad1cd9a9f
Candidate output bodies publish only when their exact cell, path, and SHA-256 have been reviewed and allowlisted and the heuristic vetoes pass. Every file still retains exact hash-bound tree metadata.