| Discovery value vs authority overread | Generated and discovered outputs widen the candidate space; any selection, decision, proof, or realization claim still needs its own rule and support. |
| Result, proposal, obtaining structure, and representation | Claim-bearing result, modal architecture proposal, obtaining A.22 structure, represented object, representation, publication form or occurrence, and presentation carrier have different identities; include only the distinctions on which the architecture use relies. |
| Search quality vs architecture adequacy | A Pareto point, benchmark score, archive member, or cluster objective can guide synthesis only through the evidence required by its branch and the rule for the next synthesis claim. |
| Model transformation vs preservation | Graph grammars and model transformations can return useful results, but the transformation claim needs its rules, source and result objects, trace and preservation/loss account. An express baseline comparison also needs the preservation relation it claims. |
| Bearer feasibility | A feasibility claim needs a viable bearer and applicable constraints. The bearer may be proposed; a claim that it actually exists requires its independent admission. |
| Reusable generator boundary | One-case generated output stays with C.35 and its declared next use; reusable-generator or mechanism-suite claims require the patterns that define or constrain those claims. |