PUBLIC PRACTICE RECORD / OCTOBER 2026

12 green. 8 red.
All 20 counted.

12 of 20 practice attempts met our strict bar (60%). These were open-source reference apps—not customer code.

Failed baselines, stopped attempts and retries stay in the denominator. The three earlier calibration runs are excluded. There were zero human code/config edits during these attempts; agents made the migration repairs.

What “green” means

• The existing test suite passes without removing assertions or adding skips; original skips are disclosed.
• The application boots, and changes across the fixed measured surface are explained.
• Combined checks catch at least 4 of 5 preselected faults, and halve the miss rate of the project tests (or retain zero misses).
• The result is achieved without human code or configuration edits.

What this does not prove

These are selected reference apps, not a random customer sample or a forecast of success. Checks mostly cover selected unauthenticated routes and specific model surfaces—not complete route or line coverage. Some upgrades were compatibility steps; some targets are now end-of-life. Green does not certify an application as bug-free or production-ready.

Rails and Spring Boot examples below passed migration checks yet scored red on fault detection. If your test coverage is too thin, we recommend tests before a quote.