Answer
Is there a benchmark showing how often a coding agent builds a working CRM with this?
No. The build benchmark protocol is designed and published, but it has not been run, so no Successful Agent Build Rate exists and any number quoted for this project is not ours (L-03). One narrower instrument has run: a tool-selection panel asking whether a coding agent picks the right framework command from a plain business goal. Its protocol was frozen and its expected outcomes pre-registered before the first run, its receipts are committed in the repository — including every cell that could not run — and it contains no success rate by design, because one measured arm is a pilot, not a comparison. It measures agent behaviour, not framework capability, and licenses no ranking. What exists beyond that is a test suite that runs on every push, covering happy paths and the policy boundaries that matter — hostile input, transaction rollback, idempotency, concurrency and immutability among them (C-20). A test count measures effort, not correctness, and real-browser tests are run manually and are not in CI.
What the ledger says, word for word
Each entry below is copied from site/claims.json, where it is bound to the evidence that holds it — a test file, a document, or a named repository fact — and to the limitation that travels with it. The answer above summarises these; these are the claim.
C-20
The verification gate runs on every push — source checks and then the whole test suite — covering happy paths and the policy boundaries that matter: hostile input, transaction rollback, idempotency, concurrency and immutability among them.
LimitA test count measures effort, not correctness — read the adversarial-review categories in docs/QUALITY_GATES.md to see what is actually attacked. Real-browser tests are run manually and are not in CI.
docs/QUALITY_GATES.mdmeasuredAgainst in this file records the run: npm run verify, green, at the commit named there, with a fingerprint of the tests/ tree it was taken over.github/workflows/ci.yml runs verify and smoke on push and pull_request, and runs the public-claims gate over full history so the measurement can be tracedL-03 · The build benchmark has not been run.
The protocol is designed and published; no Successful Agent Build Rate exists yet. Any number you see quoted for this project is not ours.
docs/strategy/CRM_BUILD_BENCHMARK.mddocs/PROJECT_STATUS.mdWhere this stops
Nothing on this page implies deployment readiness. The framework ships no authentication verifier; authorization is framework-enforced; tenant isolation is one tenant per application instance, not shared-database row tenancy. Read the exact repository posture before deployment. Every claim and every limitation is on one page, and the questions this project refuses to answer are published beside them.