# Architecture · Coverage

> This section covers how an architectural intent becomes a predicate a check can run.

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

## Entries

- [From intent to predicate](https://banes-lab.com/software-architecture/coverage/an-architecture-is-its-predicate-set.md): This section covers how an architectural intent becomes a predicate a check can run.
- [What can drift, seen through how it drifts](https://banes-lab.com/software-architecture/coverage/what-can-drift-seen-through-how-it-drifts.md): This section covers the coverage grid and its two closed axes.
- [A cell that resists an invariant](https://banes-lab.com/software-architecture/coverage/a-cell-that-resists-an-invariant.md): This section covers the walk over the grid that plans coverage, shown in [the walk], and the step in it where a cell resists an invariant.
- [The honest gaps](https://banes-lab.com/software-architecture/coverage/the-honest-gaps.md): This section covers how a rule reports what it finds and how a method declares what it lacks.