A quality attribute goal written only in a document is protected by memory and good intentions, which is to say it is not protected. A fitness function is that same goal expressed as an automated check with a threshold and a verdict, run on a schedule or on every change, so that a drift away from the goal produces a visible failure rather than a slow decline. The form is always the same: an attribute, a measurement of it, a threshold, and something that runs the comparison. A latency goal becomes a test that issues a realistic request and fails above the budgeted number. A modularity goal becomes a check that fails when a component imports something across a boundary the design forbids. A cost goal becomes a job that computes cost per unit of work and fails above a ceiling. A security goal becomes a scan that fails on a known exposed path. Not every attribute can be checked this way, and a check nobody can act on is worse than none, so choose the two or three attributes whose erosion would hurt most and start there. The point is not the tooling; it is that the design's promises stop depending on the people who remember them. You can now take a ranked attribute goal and state the measurement, the threshold, and the moment the check would run.
An architecture fitness function is an objective integrity assessment of a specific architectural characteristic (such as scalability, performance, or responsiveness), adapted from the concept of an …