| Local choices as architecture | Interfaces, modules, suppliers, and software partitions accumulate without a joint decision. | Select the project-shaping structures and make one bounded C.32.PAD decision relation with explicit receiving Work. |
| Architecture as everything important | The decision includes every design detail and unresolved issue. | Keep only selected structures coordinating several choices or protected characteristics; leave named refinement open. |
| Hard-to-change definition | Costly change alone makes an item architectural. | Name the selected structure, current alternatives, consequences, and decision use; difficulty is one possible characteristic. |
| Quality catalogue | Generic qualities are scored without bearers, conditions, Scales, or protected losses. | Create a small C.32.ACS criteria set for the current decision and preserve non-equivalent readings. |
| Metric as selector | A dashboard or eval result chooses the architecture automatically. | Interpret the reading under its subject and parity frame, then use the direct comparison and decision patterns. |
| Modularity as universal good | More modules, fewer connections, an open standard, or one supporting System is assumed better. | Compare decision-relevant consequences—for example, function bearing, coupling, cohesion, substitution, integration, evidence, cost, supply, or change—under the stated use. |
| Candidate without realization | A plausible structure lacks a needed realization dependency—for example, a transformer System, capability, interface realization, integration relation, or evidence return. | Record a bounded residual or return the unsupported branch to SYSE.3; do not hide it in an architecture label. |
| Organization mirroring shortcut | Current teams or communication links are copied into technical architecture by analogy. | Use C.32.CONWAY only for a stated influence or correspondence question; keep organization and engineered-System structures distinct. |
| Record as decision | An ADR or diagram exists, but selected option, relation, losses, and effectivity are unclear. | Recover the decision relation first; publish it afterward through the description and publication patterns. |
| Decision as actual structure | Possible-future selected content is reported as installed architecture. | Inspect the actual Systems and obtaining relations after Work; keep divergence and evidence separate. |
| Frozen architecture | Later integration or operation contradicts the basis, but the old record remains authoritative. | Apply the named reopen condition and supersede the smallest affected decision. |
| Whole-project exception | Any local refinement or residual requires centralized architecture approval. | Preserve the fixed/open boundary and escalate only changes that cross a declared structure, guardrail, or affected decision. |