# Architecture · Scale

> This section covers how work is partitioned into concerns and how many parties it needs.

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

## Entries

- [A concern is a component](https://banes-lab.com/software-architecture/scale/a-concern-is-a-component.md): This section covers how work is partitioned into concerns and how many parties it needs.
- [The ceiling moves by cost](https://banes-lab.com/software-architecture/scale/the-ceiling-moves-by-cost.md): This section covers how the ceiling on parties moves.
- [Above one tier, reduction](https://banes-lab.com/software-architecture/scale/above-one-tier-reduction.md): This section covers what happens above one tier, where a flat surface becomes the accumulation and the shape that survives is a tree, as shown in [reduction].
- [The author is probabilistic](https://banes-lab.com/software-architecture/scale/the-author-is-probabilistic.md): This section covers what architecture means when a model writes the code, as shown in three authors], and the finding that reaches the model, typed in [a…
- [Scale follows determinism](https://banes-lab.com/software-architecture/scale/scale-follows-determinism.md): This section covers how scale relates to determinism, as shown in check against care] and plotted in [cost per change], and why a model author is the case where…
- [Systems built around a model](https://banes-lab.com/software-architecture/scale/systems-built-around-a-model.md): This section covers systems built around a model, which the same canon governs with one extra category whose records sit on the correctness layer.