# Architecture

> The architecture page covers software architecture for code that an LLM writes. It models a system as a graph, types and relates its principles, traces each anti-pattern as a path of decay, derives coverage from a grid, and states every architectural intent as a condition a check can decide.

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

## Entries

- [Architecture · Model](https://banes-lab.com/api/pages/software-architecture/model.md): The architecture page covers software architecture for code that an LLM writes. It models a system as a graph, types and relates its principles, traces each anti-pattern as a path of decay, derives coverage from a grid, and states every architectural intent as a condition a check can decide.
- [Architecture · Principles](https://banes-lab.com/api/pages/software-architecture/principles.md): This section covers how a principle is held as a typed record rather than a slogan.
- [Architecture · Decay](https://banes-lab.com/api/pages/software-architecture/decay.md): This section covers how an anti-pattern forms.
- [Architecture · Coverage](https://banes-lab.com/api/pages/software-architecture/coverage.md): This section covers how an architectural intent becomes a predicate a check can run.
- [Architecture · Scale](https://banes-lab.com/api/pages/software-architecture/scale.md): This section covers how work is partitioned into concerns and how many parties it needs.
- [Architecture · Glossary](https://banes-lab.com/api/pages/software-architecture/glossary.md): Three maps place the terms below.