What to keep, what to delete, and who owns it.
A repo written in Copilot, Cursor, Claude Code, or Lovable can do the demo and still have no owner. A one-page PDF maps twelve checks onto delete, repair, and the person who stays. The audit is a separate engagement.
Get the one-page PDF
Delete
Most of what the model produced should be deleted, not refactored. A module with no caller and no owner is the first cut.
Repair
The path a customer or a payment hits cannot wait. Payments that survive a dropped call, authorization on the server, and keys out of the client are that path.
Owner
A cleaner repo with nobody named for it rots on the next generation. One person on the team owns the path that stays. If there is no such person, that is a separate seat.
What is in the PDF
Twelve checks. One page. Four for what to delete, four for the path that takes money or risk, four for who owns what stays. Three are below. The other nine are in the PDF. The check is what has to be true of the repo before a rewrite quote means anything.
Delete
A module with no owner is marked delete. "The model wrote it" is not an owner.
Repair
Authorization is checked on the server. A hidden button is not access control.
Owner
The next change has a test that fails when the behavior the business cares about breaks. A test that asserts a mock was called is not that test.
The founder's prior operating work, 2011–2024, is $20M+ in documented cost reductions across ESW Capital, Exness, Deutsche Bank, and Pepperstone. That is not an AIPIVT client result. There is no AIPIVT client listed against a generated-repo cleanup.
Email me the checklist
One page, PDF, free. The link is on the next screen and in your inbox. One email. We do not start a sequence from this form.
The checklist is ready.
Download the PDF. The same link is on its way to your inbox. A 30-minute scoping call is optional — reply to that email if you want one.
We will rewrite it.
Most of what the model produced should be deleted, not rewritten. These checks are the cut. A quote that starts from the whole tree is a quote for code nobody owns.
The tests are green.
A generated suite can assert that a mock was called and still leave the product free to break. Check 10 is that distinction. Green CI is not a reason to keep the repo.
We need someone to stay.
The checklist does not include a person, and neither does the audit. If nobody on your side can own the path, the stay-behind is a Harness Engineer on the next quote.
Common questions
Yes. One page, PDF. The form puts the link on the next screen and sends it to your inbox. One email. We do not start a sequence from this form.
No. The PDF is twelve checks. The audit is $10,000: a scored keep, repair, or delete report in 7 days. The repair is a separate quote, usually 6 to 8 weeks. We do not publish a repair price. The $10,000 does not include a person.
No, not as this cleanup. Document cleanup is a different engagement. A live agent that loops is a Harness Engineer or AI Ops seat. Pick that shape on the form and the call will say which one it is. If the tree itself has no owner, the audit still comes first.
The repo. Without it there is no audit and no engagement. Copilot, Cursor, Claude Code, and Lovable are examples of how the tree was produced, not a list we require. A legacy product nobody generated is a rebuild, not a cleanup. We do not host the app. The work is a fixed milestone. The founder is in it.