C.32.HCS:8 - Common failures and repairs

Failure	Symptom	Repair
`CatalogueAsStarterPack`	Hundreds of terms are copied into the project.	Choose the architecture-bearing family and keep only first heads that can change the next narrowing into project criteria rows.
`SoftwarePackOverfit`	Code-module terms are used for a method, role, practice, culture, or tradition without resolving the source label and rebinding bearer and scale.	Recover the described holon or the source-bearing episteme or publication context for a description-side family; name any recovery pattern actually used, then rebind bearer and scale or demote the head to source catalogue wording.
`FunctionalHeadAsArchitectureHead`	A domain function is used as the starter architecture characteristic.	Keep the function as functional demand; name the architecture characteristic that makes it sustainable.
`QBundleHeadAsScalar`	Maintainability, trustworthiness, or teachability is treated as one row.	Composite quality family work belongs to `C.25` before ACS chooses any slot.
`CatalogueCueAsStarterHead`	Catalogue maturity, benchmark performance, or dashboard cleanliness is used to admit a starter head without a rebound bearer, likely scale, Q-Bundle boundary, or first ACS question.	Keep the signal as source-looking catalogue, benchmark, or dashboard cue, ask what architecture concern worsened or disappeared, and carry the head forward only with a rebound bearer, likely scale, Q-Bundle boundary, and first ACS question.