Velocity Curve

A record of what breaks when software is built by AI.

Today, you can build software without engineers. But the problems and incidents that follow are far from rare, and the same patterns keep recurring. Most incidents cost little to prevent, but fixing the damage afterward comes at a high price.

8
Cases on file
4 failure classes
AGT

Agent control

The AI can do more than it was ever meant to.3 cases
AGT-01A coding agent used a key meant only for changing web addresses to delete the disk holding the live customer records in 9 secondsA key kept for changing web addresses could also delete storage disks, and a coding agent used it to erase the live customer records and their backups in 9 seconds.Loss9 seconds · three months of reservations · 46 minutes lost after recoveryAGT-02Text inside a filed bug report took control of the build machine, and a publishing key left valid shipped an unauthorized update to usersAn automatic helper on a public code project could be set off by any stranger and ran what a filed report told it to, and eight days after the flaw was published an unauthorized version reached npm users.Loss2.3.0 · roughly eight hours liveAGT-03Salesforce's AI assistant treated a stranger's text in a public form's long message box as instructions to carry outA public lead form's long message box carried a stranger's written requests into an AI assistant that read customer records, and the assistant worked through them alongside the staff member's own request.Loss42,000 characters · severity 9.4 · $5 domain
OPS

Operations

Nothing is in place for shipping, watching or recovering.1 case
OPS-01A standing yes given in advance let an AI coding agent's wipe-everything command erase the live system the course platform ran onAn approval given in advance covered every setup command, so a wipe-everything command erased the live course platform and its nightly database copies; AWS located a copy and restored it.Loss2.5 years of submissions · 1,943,200 rows restored · 24-hour outage · +10% cloud cost
ACC

Access control

The rules for who can see and change what are never enforced.2 cases
ACC-01Base44's sign-up path accepted an app identifier anyone could copy from the web address, and let outsiders create working accounts inside private company appsA private app's identifier sat in plain view in its web address, and the sign-up path treated knowing it as permission, so outsiders could create confirmed accounts inside company apps.Lossaround five public web addresses · two open documentation pages · fixed in under 24 hoursACC-02A database key printed inside Moltbook's own web pages opened every table, because the per-record permission rules were never switched onA social site for AI agents shipped a database key inside the pages it sends to every visitor, and with no per-record permission rules turned on, that key read and changed every table.Loss1.5 million tokens · 46,631+ emails · 4,060 private conversations · 4.75 million records
SEC

Security

Keys, credentials and identity are left where they can be taken.2 cases
SEC-01A key left in a code project's saved history kept running up charges for months, with nothing to cap them, until a student's bill reached 55,444.78 USDA student's API key stayed live in a shared code project's history while charges climbed to 55,444.78 USD, and the first warning came from a stranger.Loss$55,444.78 · 14,200+ requests · 100 % failedSEC-02Keys left in publicly readable code still opened 321 n8n setups, because taking a key out of the current files does not switch it offKeys for automation setups sat readable in old published code, and when they were tried, 321 of the 896 setups that answered still let them in.Loss4,576 keys · 1,255 setups · 321 of 896 accepted

How cases are handled

  • 01Evidence, not anecdote. Every case is filed against a primary source — the original disclosure, report, or the builder's own account.
  • 02The subject is never named. Companies and platforms already reported publicly are named. Individuals are not, ever.
  • 03A case has a determination. Not a summary — a stated cause, in one sentence. If it cannot be written that way, it is not yet a case.
  • 04Losses are stated as reported. Where a figure was never established, the entry says so rather than estimating.

Which of these describes your system?

That is the one question these cases cannot answer for you. Bring it to a free 30-minute call: we read what you actually built and tell you, in plain language, which failure classes are present, which are likely, and which you can safely disregard.