Proof

Don't take our word for it. Check the receipts.

Two questions are worth asking about any coding agent. Can it deliver working software without a person watching every step? And, before it touches a system that matters, can it tell you the truth about that system? Each has its own proof, and both are public.

Track 1 · The agent, unattended

What the method delivers

The Silicon Exchange case study shows a 27-billion-parameter model on one laptop building and verifying a complete web application unattended, inside CodeLead's governed loop. The application and its full git history are public.

  • 17 / 17increments verified, each gate-checked
  • 30 / 30business-rule oracle cases, checked independently of the model's tests
  • 0unsafe applies across 350+ benchmarked runs
  • ~3 minfor a governed change to a 17-year-old C# library, build green

Track 2 · Legacy assessment proof

What a read-only assessment finds

The sample Dossier surveys three real .NET code bases for a fictional holding company. It shows the work the assessment is built on: business rules lifted from the code with their source lines, dependencies mapped, risks ranked, and a phased migration sequence with a proof step for every phase.

  • 168business rules lifted from code, one enforced two ways
  • 63coding patterns to clear before behavior can be locked in
  • 61%of the survey tool-driven, and every section says which part
  • 12modernization types assessed per system, each fit with an estimate, its basis and its confidence

Why two tracks

The case study is why the method holds. The Dossier is where a modernization starts.

The case study is a technical field report for anyone who wants to see what a governed local model can and cannot do, including what it does not prove. The assessment is the first step for a business-critical system. They answer different questions.

A third piece of evidence is still a preview: the knowledge base, shown running on real data from our benchmark project.

Run it on your own code.

The CLI is in private beta. For a legacy system, the same survey runs read-only on yours.