Evaluation boundary: Use ADA only to evaluate architecture-decision adequacy for a declared use. It does not perform candidate synthesis, comparison, selection, selected-set result declaration, actual publication, local choice, evidence support, assurance, gate passage, governance enforcement, or pattern-quality evaluation.
Decision and projection boundary: Use C.32.PAD to repair the decision relation and C.32.ADR to repair ADR-like publication projection.
Description and structure boundary: Use C.30, C.30.AD, and C.30.ASV for architecture claim, description, and view adequacy.
P2S docking: Use C.32.P2S when a weak decision-adequacy row must reopen the connected architecturing flow rather than only repair the decision record.
Method and work boundary: Use A.15, A.15.1, A.15.2, A.15.5, E.8, E.11.PUR, and C.24 for method, work, readiness, pattern-use, and agentic tool-use claims.
Characteristic and eval boundary: Use C.32.ACS, C.32.HCS, C.25, C.32.ACE, C.16, C.31, and C.31.ASAP for characteristic rows, Q-Bundles, eval-program framing, typed measurement or evaluation results, modularity, and scale preference. ADA may inspect references to those objects as coordinate evidence; use their subject patterns for any definition change or actual operation.
Evidence, assurance, gate, and governance boundary: Use A.10, B.3, A.21, and local governance patterns when those claims are live.