Chapter 20.4 · Assembly keeps component origins

Why this matters

A parent assembly’s history depends on its individually identified components and their changing roles.

The aerospace story motivates long-lived traceability, but a current list of parts is not a complete installation history.

Step by step

1. 01

   Inspect an origin/context bond

   Screen or control: P1 GIAI/CPI roles and P5 sensor context

   Why: Installed role must not erase the incoming physical asset.

   How: Locate the supplied sensor context and its source-asset relationship. Record both addresses and the missing real installation evidence.

   What you should see: A two-identity-plus-bond explanation.

   Verify: The supplier identity is not renamed into the installed CPI.

2. 02

   Draft a replacement history

   Screen or control: Chapter 20.4 assembly and service table

   Why: A replacement changes the active role, not the existence of the former component.

   How: Sketch old-component removal and new-component installation as appended proposed transitions. Include actor, time, work-order, source and validity fields as requirements.

   What you should see: A history-preserving change plan.

   Verify: Old records remain retrievable and no dates are invented.

What is happening under the surface

Current governance preserves supplier GIAI → installed CPI → parent GIAI as distinct records with a first-class bond.

Installation, removal and replacement need separate events, actors, evidence and validity intervals. Old identities and bonds remain addressable after a change.

Common mistakes

• Flattening all components under the parent’s model name.
• Replacing an original physical identity when a component is removed or reused.

The records an agent needs

The sample illustrates the identity bond but has no verified installed aircraft part, removal event or temporal service history. Current rules add explicit transition requirements.

Pointers locate records; hashes pin bytes; lesson numbers locate teaching material. None substitutes for an applicable assigned GS1 identity.

Apply what you learned

Design a two-component replacement timeline with preserved origins.

Prepare these outputs

• Old/new physical identities
• Installed contexts
• Proposed transition events and intervals
• Missing verification/authority evidence

Review your work against these checks

• The original source identities survive
• Removal is not deletion
• No aircraft safety or service qualification is claimed

Source and current boundaries

Chapter 20.4 · future vision. Adapted, anonymous teaching prose; not a quotation or independent verification of the author’s assertions.

Source part word/document.xml; original document SHA-256 71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f. Exact paragraph/table locators are retained; page numbering is not verified.

The assembly story is a conceptual exercise, not aerospace engineering guidance, airworthiness proof, certified parts data or an implemented aircraft system.

Current governance adds exact-source retention, unknown-state, disclosure, validation and scoped-authority safeguards. Those safeguards are not represented as quotations from the historical book.

Numeric lesson numbers are educational content locators, not GS1 identities. Linked public screens use an anonymous non-issued fixture; reading, retrieval and practice do not authorize physical/cloud execution or constitute model-weight training.

Reading, answering a question and opening a diagram do not issue identifiers, validate a scientific method, establish company authority, commission an environment or authorize physical action.