Image
MVP to Stable

What an AI-built codebase is missing (the assessment checklist)

The product works, but nobody can say which parts are safe to touch. This read-only assessment lists what an AI-built codebase lacks, with the evidence for each finding, and changes nothing: your product owner decides what happens next.

The short answer

Short answer

The usual gaps in an AI-built codebase are tests, review discipline and a record of what the model decided.

A read-only assessment checks for those three, plus secrets kept in the code, an unknown dependency list and errors nobody hears about. It writes each gap down as a finding with its evidence and changes nothing.

Today

What goes unseen until the first serious change?

Your product works and people use it. Nobody, you included, can point to the parts that are safe to change, because the model that wrote most of it kept no notes and the person who prompted it has moved on to the next feature. The gaps stay invisible until the first serious change or the first outside review, and then they arrive as a surprise instead of as a list.

Who asks for this inventory?

A founder or technical lead with a working AI-built product who suspects it is fragile and wants a named list of gaps before spending on fixes. It also suits a team about to hand the code to an engineer who was not there when it was built.

What does each finding carry?

The output is a findings report. Every entry in it has the same parts, so a worry becomes something a person can check.

Part of a findingWhat it recordsWhy it is thereWho uses it
What is absentA plain statement of the missing pieceSo the gap has a nameYour product owner
Where it was seenThe file, module or setting where the absence showsSo anyone can go and lookYour engineers
EvidenceWhat was read, and what was missing thereSo anyone can check the findingAnyone reviewing the report
Published referenceThe public standard that names the same concern, where one existsSo the finding rests on more than one reader's opinionYour owner and any outside reviewer
Proposed orderAn optional suggestion, labelled as a proposalTo help the owner sequence, never to bind themYour product owner
Owner's rulingAccepted or rejected, by nameSo nothing moves on a finding nobody acceptedWhoever acts next

How it works, step by step

Each step below is one thing the assessment looks for. It reads only what you share and writes down what is absent.

01

Check for tests around what users rely on

Whether the behaviour your users depend on is checked by automated tests, or only by someone clicking through before a release.
02

Look for a review trail

Whether each change was read by someone other than its author before it shipped, and whether that reading left a record anyone can find.
03

Look for a record of the model's decisions

Whether the prompts, choices and trade-offs behind the code exist anywhere outside the code itself, or were lost with the chat that produced them.
04

Find where secrets live

Where keys, passwords and environment settings are kept, including the repository's history, where a key deleted from today's code can still be read. OWASP's Secrets Management Cheat Sheet observes that many organizations have secrets hardcoded within the source code in plaintext.
05

Take a dependency inventory

What the code depends on and at which versions, including dependencies of dependencies. CISA describes a software bill of materials as a nested inventory, a list of ingredients that make up software components. The OWASP Top 10 for 2025 lists not tracking the versions of all components you use as a sign of exposure to software supply chain failures. An external system nobody documented is recorded here as one finding; building on such a system is a separate subject.
06

Check whether failures reach a person

Whether errors reach a log or an alert that someone actually reads, or disappear. The same OWASP list states that without logging and monitoring, attacks and breaches cannot be detected.
07

Human gate: your owner rules on every finding

The findings report goes to your named product owner, who accepts or rejects each finding and decides what, if anything, happens next and in what order. The assessment changes nothing, merges nothing and schedules nothing. How It Works describes where that authority sits. Approval gates sets out why a sign-off belongs to one named person.

Scope

What does a read-only assessment leave out?

No edits

It writes a findings report and touches no file. The code you hand over is the code you get back.

No probing of outside systems. An external dependency is listed; how it behaves is a separate piece of work.

No scores

A finding says what is absent and where. It does not grade the product or rank it against others.

No certification

For the security items, the OWASP Application Security Verification Standard provides developers with a list of requirements for secure development, and you can read the findings beside it. Reading the findings beside a standard does not mean the product passes it.

Where this fits

MVP to Stable

This is the front of the MVP to Stable offer: for a product already built with AI that works, mostly, and now needs hardening into something a team can change with confidence. A vibe-coded MVP is AI without governance, and the first three steps above are that diagnosis applied to code. Acting on accepted findings, one reviewed change at a time, is what the hardening page in this series covers. If your question is about a process rather than code, the checklist for whether a workflow is ready for an agent is the one to run, and the library of use cases has the rest.

MVP to Stable Product
How It Works

Questions, answered

No. It is read-only, and the findings report is the whole of its output. Any change is a separate decision your product owner makes afterwards.
AI Opportunity Audit · Codebase assessment

Find what your codebase lacks before you change it

Bring the codebase you are least sure about and get a findings report on what it lacks.