Receiving uses:C.32.P2S problem-to-structure architecturing flow, C.32 candidate synthesis, C.32.MLAO multilevel residual work, C.32.CONWAY correspondence frames, C.32.FAIL repair cues, C.32.ACE eval programs, A.19.CPM comparison inputs, A.19.SelectorMechanism selection inputs, C.11 local choice inputs, inputs for selected-set result declaration under G.5, source-backed publication-face and source-return inputs under E.17, publication-occurrence and audience-availability inputs under E.24.PUB, and architecture-decision inputs for C.32.PAD.
Starter-pack boundary: Use C.32.HCS when the project needs a holon-family starting set before criteria rows exist.
Q-Bundle boundary: Use C.25 when the architecture characteristic is really a composite quality family with several measures, scope slots, mechanisms, statuses, qualification windows, or evidence.
Scale-preference boundary: Use C.31.ASAP when a project claims that one architecture alternative is preferable over another under a declared scale window; the ACS row supplies a criterion, not that preference.
Eval boundary: Use C.32.ACE when a project wants eval-program framing over declared rows, Q-Bundle slots, candidates, or selected-structure changes; state each actual typed result separately under the pattern that defines and tests its kind and exact predicate or constraint.
Measurement boundary: Use C.16 when a reading, coordinate, unit, threshold, score, or cross-case comparability claim is made.
Structural-information boundary: Use C.33 or C.34 when the issue is captured structure, lost structure, or preservation adequacy before a criterion row exists. Use C.32.ACS only when that structural-information or preservation concern becomes a declared architecture-characteristic criterion row. Use C.35 only for kind restoration and architecture-use adequacy of a generated or discovered result before C.32 or ACS uses a criteria-bearing claim based on that result.
Proxy boundary: Use E.13 when an optimization indicator, score, eval result, or dashboard state begins to replace the declared architecture concern.
Synthesis boundary: Use C.32 after criteria rows exist and the next useful work is to synthesize candidate selected-structure changes.
Decision and publication boundary: Use A.19.CPM for comparison, A.19.SelectorMechanism for selection, C.11 for choice, G.5 for selected-set result declaration, and C.32.PAD for an architecture decision. For publication, use E.17 for a source-backed face and source return and E.24.PUB for the publication occurrence and audience availability.