software-architecture CAP-0045 · active

Making design decisions that hold up as a system grows

Whether a model can choose structure — module boundaries, interfaces, data flow — that stays maintainable, as opposed to code that passes the tests today; the failure is locally correct code that raises the cost of every later change.

Tags: coding-agent

Filed from Russ's capability map (2026-09-12). Almost every coding benchmark measures whether tests pass, which says nothing about whether the change was made in the right place or made the next change harder. Lehman's law, filed as an adage, predicts the cost. Evidence here is scarce because the property is slow to measure; that is the research brief.

What counts as this capability

Scope boundary used when deciding whether a paper is really about this capability, rather than merely mentioning it.

In scope when the paper measures maintainability, structural quality or the cost of later changes in model-written code, or compares model design choices to expert ones. NOT in scope for test-pass rates alone or for style and formatting.

Claims

Techniques

None yet.

Sources

Every paper, post or observation behind this capability. Ones cited by a claim show the claim and its stance; ones filed directly are about the capability but have no claim drafted from them yet. Open one to add support or contest it.

Suggest a change

Capabilities are a way of carving up the subject, and carvings are arguable. Say so if this one is wrong — especially a proposed one, which a pipeline added because several papers used the same framing, not because anyone decided it was right.