C.32.ACS:9 - Consequences

Consequence	Benefit	Cost
Architecture optimization gets declared criteria.	C.32 and C.32.MLAO can use multi-criteria language without unnamed criteria.	The project must admit and type rows before synthesis or optimization claims.
The 300-to-3 problem is handled by staged admission.	Broad catalogues inform the project without serving as the project criteria set.	Some familiar qualities must be guardrails or context rows.
Anti-Goodhart guardrails are explicit.	Optimization can protect functional adequacy and other architecture concerns.	A single convenient score cannot govern choice by itself.
Measurement and eval stay clean.	C.16 and ACE keep readings, eval programs, and eval results separate from criteria.	Some eval programs require additional receiving-pattern work before they can drive action.
Q-Bundle structure stays clean.	Composite quality families keep their C.25 structure.	ACS cannot shortcut a composite family into one scalar row.