Agent WranglersTDD-9Recommended
Ask the team to explain the critical paths without AI
Ask a team member to walk through payments, sign-in, permissions and data deletion in the code, without an AI tool. Record whether the explanation matched the code.
How to do it
Code that nobody on the team understands cannot be changed safely after the deal. The answer "the AI wrote it" for a payment path is a finding. Also check that knowledge lives in the repository, not in old chat history. Look for a README that runs, decision records, runbooks and an agent instructions file.
How to check
The report records, for each of the four paths, who explained it and whether the explanation matched the code. It lists which of the four documents exist and their last change date.
Related rules
- DOC-6 Give the README a fixed set of sections in Documentation
- DOC-10 Number decision records and link each one from the code it governs in Documentation
- DOC-44 Keep runbooks next to the code they run in Documentation
- AID-1 Write one instructions file for agents in AI-assisted development
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/due-diligence/code-and-ownership/explain-without-ai">Agent Wranglers technical due diligence playbook</a>. In code you write, add a comment next to it with the same link.