# Bane's Lab — Structured collaboration with LLMs

> Bane's Lab documents a method for building software with LLMs, together with the instruction format (Pattern Abstract Grammar), the software architecture and the ontology the method relies on.

Canonical: https://banes-lab.com/

Bane's Lab

# Structured collaboration with LLMs

Bane's Lab documents the method I use to build software with LLMs, together with the instruction format, the software architecture and the ontology that the method relies on. I have used it since 2024, on every project I build, this site included. The method does not make a model's output correct. What it does is make incorrect output visible and refuse it, through checks that run on every change rather than through instructions the model is asked to remember.
[Start with the method](/disciplined-methodology) [Read the grammar](/pag) [Every page as JSON and Markdown](/llms.txt)

## How the site teaches

The site is organized around the methodology, which is one page of six tabs read in order, from Start to Ship. The grammar, architecture and ontology pages supply material that particular sections of the methodology rely on, and the visualization shows where each of their sections enters that order. The anatomy page works in the other direction: it shows the source of this site, and its sections link back to the chapters that describe it.

**66** rules enforced on every change

**94** steps in one verification run

**446** architecture principles

**1357** defined terms

## Methodology · Disciplined Methodology

The method itself comes in six parts that follow the order of the work, from starting a project to shipping it. Each section describes one practice, how it fails when it is missing, and a test you can run against your own work to check it.

- [Start](/disciplined-methodology)
- [Plan](/disciplined-methodology/plan)
- [Build](/disciplined-methodology/build)
- [Verify](/disciplined-methodology/verify)
- [Collaborate](/disciplined-methodology/collaborate)
- [Ship](/disciplined-methodology/ship)
- Engineering leads · Software architects · LLM-assisted developers
[Read the method](/disciplined-methodology)

## PAG · Pattern Abstract Grammar

Pattern Abstract Grammar is a structured format for writing instructions to a model. A document declares what type of instruction it is, draws its verbs from a closed vocabulary and ends every step on a gate with checkable evidence. The page covers the grammar, its validation rules and a set of templates.

- [Introduction](/pag)
- [Guide](/pag/guide)
- [Orchestration](/pag/orchestration)
- [Patterns](/pag/patterns)
- [Keywords](/pag/keywords)
- [Grammar](/pag/grammar)
- [Validation](/pag/validation)
- [Templates](/pag/templates)
- Software architects · LLM-assisted developers · Tool authors
[Read the grammar](/pag)

## Architecture · Principles, decay and coverage

The page covers software architecture for systems in which a model writes much of the code. It models a system as a graph, holds each principle as a typed record, traces each anti-pattern back to the control whose absence caused it, and derives coverage from a grid rather than from a count.

- [Model](/software-architecture)
- [Principles](/software-architecture/principles)
- [Decay](/software-architecture/decay)
- [Coverage](/software-architecture/coverage)
- [Scale](/software-architecture/scale)
- [Glossary](/software-architecture/glossary)
- Engineering leads · Software architects · LLM-assisted developers
[Read the architecture](/software-architecture)

## Ontology · Principles, lexicon and algorithms

The ontology is the data behind the architecture page, and the site's own checks read it too. It holds every principle with its relations and repairs, every defined term, every algorithm contract, and how each tension between two principles is resolved.

- [Principles](/ontology)
- [Lexicon](/ontology/lexicon)
- [Algorithms](/ontology/algorithms)
- [Reasoning](/ontology/reasoning)
- [Schema](/ontology/schema)
- Software architects · LLM-assisted developers · Tool authors
[Open the ontology](/ontology)

## Anatomy · Source trees, walks and definitions

The anatomy page shows the client source of this site, parsed on every build. Each file is shown with its syntax walk, its definitions and the calls between them, together with the diagnoses the parser ran over the whole tree.

- [Reading](/anatomy)
- [Site tree](/anatomy/tree)
- [Build tree](/anatomy/build)
- [Coordination tree](/anatomy/coordination)
- Software architects · LLM-assisted developers · Tool authors
[Open the anatomy](/anatomy)

## FAQ · Origin, practice and limits

Here I answer the questions I am asked most often about the methodology, including where it came from and where it stops being useful.

- [Licensing](/licensing)
- [Info](/info)
- [Terms](/terms)
- [Privacy](/privacy)
[Read the FAQ](/faq)