The Readiness Certificate

One page. Plain language. The answer a manager actually needs: is this codebase safe for AI yet, and what's the shortest path to yes?

payments-service
Certified by ReadyBase v1.4.0 · sample
AI-viable
72
Grade B / 100
VerdictReady for AI-assisted dev
Risk levelModerate
Effort to AI-viable (≥60)Already there
High-risk files3 of 248

Top high-risk files (hubs without tests)

internal/billing/charge.go37 dependents · no tests
internal/auth/session.go20 dependents · low coverage
internal/ledger/post.go14 dependents · high complexity

Pre-flight checklist, highest-impact fixes

Add tests to billing/charge.go. The biggest hub with zero coverage, the single highest-leverage fix.
Add a CI readiness gate. Stop the score from silently regressing on future PRs.
Raise the bus factor on auth/. Single-owner code, pair or document before it becomes an incident.
Re-run after each round of fixes to track progress. Generated locally · no code transmitted

Why it lands

A go / no-go in plain words

No code to read. A decision-maker gets a verdict, a risk level, and a number they can act on.

The few fixes that matter

Not an overwhelming list, the 3-5 highest-impact gaps, ordered by leverage.

A progress tracker

Idempotent. Run it again after fixes and watch the verdict and score improve.

readybase certify .

Generate your own in one command. Get started →