A41 · Reference edition 2026.11
Component stacks — Definition and boundaries
A stack record needs an ordered sequence from the base to the part contact. Component IDs alone do not establish assembled height.
Scope and purpose
Start by separating the named concept from adjacent concepts. Use the observation below to identify the question the record is intended to answer. Read the caution before applying the example. A definition is useful only when another reader can tell what falls outside it.
Working notes
This reference collection concerns light, offline dimensional-inspection layouts. It brings locating concepts, component descriptions and revision records together without substituting for an engineered fixture design. The drawings are original explanatory diagrams. Reference IDs identify documents, not commercially tested products. Read the scope and limitations alongside each example, and keep the actual part drawing and inspection requirements available when reviewing a proposed layout.
Practical example
List base interface, riser, support body and contact cap as separate rows.
| Reference record | Interpretation |
|---|---|
| A41 | Component stacks |
| Scope and purpose | A stack record needs an ordered sequence from the base to the part contact. Component IDs alone do not establish assembled height. |
| Limits and interpretation | Do not sum nominal catalogue heights into an unsupported tolerance claim. |
Review checklist
Write a one-sentence scope statement; identify a neighbouring concept; record what the example does not establish.