Decision boundary: Use C.32.PAD for the project architecture decision relation. C.32.ADR publishes an ArchitectureDecisionDescription@Project; it is not generic ADR guidance and not a second decision authority.
Structural-information boundary: ADR-like projections may cite C.33 or C.34 to show captured structure, lost structure, or preservation adequacy behind the projected decision. Cite C.35 for the exact generated or discovered result, the obtaining or proposed organization, its next-use condition, and the limit or return. Resolve representation, publication-form, or carrier questions separately when the receiving use depends on them. The ADR projection publishes a decision description; use C.32.PAD for the decision relation and C.35 for the cited result’s admissible architecture use.
P2S docking: P2S may cite an ADR projection as one stage where decision, rationale, method expectation, and source-return are published for readers; ADR does not carry the whole architecturing flow.
Architecture-description boundary: Use C.30.AD and C.30.ASV for architecture-description and view adequacy. ADR carries refs and reader-use slices, not full description authority.
Pattern and method boundary: Use E.8 when the published object is an FPF pattern, E.11.PUR for pattern-use recommendation, and A.15 for method and work claims.
Publication boundary: Use E.17 for MVPK faces and source return, and E.24.PUB for publication occurrences, forms, carriers, bounded use, and audience availability.
Evaluation boundary: Use C.32.ADA for decision adequacy; use C.32.ACE, C.16, A.10, B.3, or A.21 for eval, measurement, evidence, assurance, or gate claims.
Package boundary: A record package map aids navigation among records. It does not decide active architecture by file order; PAD relations and status refs remain governing.