# Architecture · Model

> 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/model

## Entries

- [A system is a graph](https://banes-lab.com/software-architecture/model/a-system-is-a-graph.md): This section covers the model the rest of the page evaluates, in which a system is a graph and a question about the system is a question about reach, answered…
- [Definitions own what, code owns how](https://banes-lab.com/software-architecture/model/definitions-own-what.md): This section covers the split between definitions and code.
- [The layer spine](https://banes-lab.com/software-architecture/model/the-layer-spine.md): This section covers the layer spine, the one axis along which systems decompose, running from domain through application, processing, runtime, infrastructure…
- [The direction axis](https://banes-lab.com/software-architecture/model/the-direction-axis.md): This section covers the direction axis, which says who may depend on whom, as shown in one way], while the classification described in [the layer spine says…