| Architecture-as-actor | Replace the acting architecture with the exact U.System. When performance is claimed, recover every precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is current, and state any actor-side or Work-to-change relation separately. Keep architecture relation, claim, holon, and selected structure as separately related influence-side objects. |
| Influence-as-performance | Remove system-role-kind, assignment, Work, performer, or transformation-participation inferences that came only from influence. Establish those facts independently or leave them absent. |
| Changed referent or transformation omitted | Identify the exact continuing referent; when actual change is claimed, identify its A.3.4 U.Transformation; keep actor-side and Work-to-change relations under their subject patterns before deciding which architecture content is transformed. |
| Performer without Work basis | When performance is claimed, recover every precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is current, and add only the other direct relations used by the claim. Use A.15.1 multiple-performer forms when needed. |
| Influence source without governor | Apply the direct relation pattern. With no kind/predicate, keep the correspondence synthesis-local and return missing-governor; with unresolved facts, name the grounding boundary; with a false predicate, remove the influence-occurrence claim. |
| Architecture-bearer equality with an actor inferred | Keep the influence-source holon and acting-system refs separate; assert equality only when independent actor and architecture-bearer facts establish it. |
| Transformed-side-only inverse Conway | If the text says inverse Conway but changes only the transformed architecture, name the exact influence-source selected structure that must change or stop using the inverse-Conway claim. |
| Source-side change without transformed pressure | If an organization, method, line, or toolchain is reorganized without one transformed architecture and characteristic under pressure, return to the direct Work or organization-design use. |
| One-sided optimization | Prepare source-side change, transformed-side change, joint change, and bounded mismatch candidates before claiming the correspondence has been constructively handled. |
| Pair treated as network | Keep the exact pair row as one qualified reading; use E.18.NET for network identity, members, and exact cross-flow relations. |
| Network citation treated as relation admission | Ground the exact relation participants in member-flow positions and make the E.18.NET composite locator name that same citing current record and exactly one cross-flow row; otherwise remove networkCrossFlowRelationRowRef. A locator for one record does not qualify another record’s citation. |
| Mirroring treated as adequacy | Keep the statement as candidate pressure or use C.29 when structural similarity or preservation is claimed. |
| Software-practice overfit | When the changed referent is a product family, manufacturing system, school, hospital, or another admitted non-software holon, transfer only the selected-structure correspondence and affected characteristics; do not import software-service or team ontology. A method-family or method-description label alone does not make the named object a U.Holon; if the case uses a method-related holon, identify that exact holon and admit it independently under its direct kind-admission pattern. |
| Static correspondence | Reopen when either architecture, selected structure, relation occurrence, changed referent, or evolution window changes. |