C.32.MLAO:12 - Relations

• Builds on: C.30.ILC for residual triage, C.32 for palettes, C.32.ACS for architecture-characteristic criteria rows, C.32.ACE for eval programs and eval results, C.29 for mathematical-lens use when claimed, A.19.CPM for explicit comparison, A.19.SelectorMechanism for set-returning selection, C.11 for local choice over an existing option set, G.5 for selected-set result declaration, C.19.1 for scale-amenability preference claims, and C.31 or C.31.ASAP for characteristic or scale-preference claims.
• Uses: E.10.ARCH and C.30.STRAT when stratification terms hide the recovered neighborhood; E.10 and B.2.P when BOSC, emergence-family, MHT, MET, MFT, boundary-crossing, or promotion-like wording hides the claim kind; B.2 when the candidate creates, reidentifies, splits, joins, or changes the relevant whole after existing-whole explanations are insufficient; C.32.CONWAY when residual reduction requires co-synthesis of exact influence-source and transformed-side architecture content; A.6.M, C.30.LCA, C.30.TFS-REL, and method or work patterns when their structures are the affected selected structures.
• Patterns for the next questions: A.19.CPM for explicit comparison, A.19.SelectorMechanism for set-returning selection, G.5 for selected-set result declaration, C.11 for fixed local choice, C.30.AD for architecture-description work, E.17 for a source-backed publication face and source return, E.24.PUB for the publication occurrence and audience availability, and C.32.PAD for project architecture decisions.
• P2S docking: C.32.P2S uses MLAO when cross-scope, interlevel, interlayer, or meta-holon residual pressure must become candidate-synthesis and repair content inside the wider architecturing flow.
• Boundary: Use C.32.MLAO only for residual-reducing architecture candidate frames after residual triage. Use the applicable patterns for mathematical-lens adequacy, evidence, assurance, gate passage, ethical mediation, causal claim adequacy, work authorization, and final selection.