# Architecture · Decay

> This section covers how an anti-pattern forms.

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

## Entries

- [An anti-pattern is a decay path](https://banes-lab.com/software-architecture/decay/an-anti-pattern-is-a-decay-path.md): This section covers how an anti-pattern forms.
- [Seven controls, seven classes](https://banes-lab.com/software-architecture/decay/seven-controls-seven-classes.md): This section covers the seven controls, each of which owns a decay class, as shown in seven controls] and typed in [an anti-pattern record].
- [Never and always](https://banes-lab.com/software-architecture/decay/never-and-always.md): This section covers why every avoidance rule is written as a pair, as shown in one inversion].
- [Debt and leverage](https://banes-lab.com/software-architecture/decay/debt-and-leverage.md): This section covers the consequence on each side of an inversion, which lets the rule survive the moment it is inconvenient.