# Methodology

> Disciplined Methodology is a method for building software with LLMs: one loop at every size, rules held by checks rather than attention, state derived rather than written, and evidence in place of claims.

Canonical: https://banes-lab.com/disciplined-methodology
Page as Markdown: https://banes-lab.com/disciplined-methodology.md
Page as JSON: https://banes-lab.com/json/disciplined-methodology
This index as JSON: https://banes-lab.com/json/api/pages/disciplined-methodology

## Entries

- [Methodology · Start](https://banes-lab.com/api/pages/disciplined-methodology/start.md): Disciplined Methodology is a method for building software with LLMs: one loop at every size, rules held by checks rather than attention, state derived rather than written, and evidence in place of claims.
- [Methodology · Plan](https://banes-lab.com/api/pages/disciplined-methodology/plan.md): Before any work starts, one gate decides whether it starts at all.
- [Methodology · Build](https://banes-lab.com/api/pages/disciplined-methodology/build.md): Seen from outside, the work is one cycle, as shown in the loop from outside. The tools run with their fixers on and report what the fixers could not repair.
- [Methodology · Verify](https://banes-lab.com/api/pages/disciplined-methodology/verify.md): The most expensive failures I have had were the ones that looked right: the code read well and the model said it was done, but nothing had run.
- [Methodology · Collaborate](https://banes-lab.com/api/pages/disciplined-methodology/collaborate.md): This section covers how the developer and the model reach each other.
- [Methodology · Ship](https://banes-lab.com/api/pages/disciplined-methodology/ship.md): One command runs every tool in this method as a single gate, in stages typed as shown in a stage array.