A44 · Reference edition 2026.11
Component stacks — Recording and revision
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
A reference record should allow another reader to reconstruct the intended description. Keep the identifier, context and revision together. When information changes, explain the change and retain enough of the earlier description to understand what was superseded.
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 |
|---|---|
| A44 | 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
Check the identifier; describe the observation and its source; date the revision; link affected figures; distinguish confirmed facts from open questions.