How easily developers can read, understand, and safely change a codebase over time — driven by clarity, structure, and test coverage.
Example: Clear naming and small functions vs. a 2,000-line function called doStuff().
In practice: It's notoriously hard to measure directly, so teams often lean on proxies like cyclomatic complexity, test coverage, and code review turnaround time as stand-ins.