Follow the sensor identity into its component context

Why this matters

A thing can become part of another thing without losing its original identity.

An installed-context proposal and observed physical installation need different evidence.

Step by step

1. 01

   Inspect the component identity

   Screen or control: CPI · Component / part

   Why: The installed occurrence is not a replacement for the incoming asset.

   How: In P1 choose CPI and inspect the retained thermal sensor context. Record the urn and CPID key-type value exactly as displayed.

   What you should see: The CPI urn is urn:epc:id:cpi:0614141.414141.41.

   Verify: Keep the CPI context separate from both sensor and parent GIAIs in your notes.

2. 02

   Open the exact CPI graph context

   Screen or control: Lesson link · CPI focused graph

   Why: Exact node addressing avoids resolving a similar sensor label.

   How: Open the focused CPI graph link below. Inspect its exact source ID and source occurrence pointer.

   What you should see: P5 selects the existing CPI node and shows an explicit direct-neighbor viewport subset.

   Verify: The selected node is #/P5/nodes/3 in the package and the complete graph count remains 329/231.

3. 03

   Traverse the original sensor bond

   Screen or control: Original direct relationships · installed as context

   Why: The supplier asset identity must survive the new context.

   How: In the CPI inspector open the incoming installed-as-context relationship. Read Subject, Destination, asserting actor, scope and assertion time. Open Subject to inspect the sensor GIAI.

   What you should see: The source subject is urn:epc:id:giai:0614141.100002; the destination is urn:epc:id:cpi:0614141.414141.41.

   Verify: Record relationship GDTI 00900.2 and #/P5/edges/1; authority stays unknown and assertion time stays unknown, not “now”.

4. 04

   Traverse to the parent

   Screen or control: Original direct relationships · component of · Destination

   Why: Parent membership is a typed assertion, not identity equivalence.

   How: Return to the CPI context, open component-of, then inspect its destination cycler.

   What you should see: The parent is urn:epc:id:giai:0614141.4; relationship GDTI 00900.3 remains separately addressable.

   Verify: Show three nodes and two directed relationships in your receipt. State that the fixture proves retained structure, not physical installation.

What is happening under the surface

The sample sensor GIAI is distinct from its CPI occurrence and from the parent cycler GIAI.

The graph preserves installed-as-context and component-of as separately identified directed assertions.

These example assertions are authored, with unknown authority and null assertion time. This public fixture does not supply an observed EPCIS installation event or replacement history.

Common mistakes

• The word installed in a candidate label is not observed-installation proof.
• Do not invent an EPCIS event or removal date because the relationship type suggests a lifecycle.
• Do not use a shared prefix or label as evidence of ownership or sensor compatibility.

The records an agent needs

The incoming GIAI → CPI → parent GIAI path references original nodes. Do not collapse it into one “sensor” row. Current installation validity, observed event time and supersession history are not supplied here and remain gaps.

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

Apply what you learned

Write a bond-traversal receipt that would let an agent retrieve both the incoming identity and component context.

Prepare these outputs

• All three node IDs and two relationship IDs.
• Directed endpoints, source/actor, assertion time and authority states.
• The additional observed event, validity and installation evidence needed for a real deployment.

Review your work against these checks

• The sensor GIAI remains recoverable.
• The CPI is represented as context, not identity replacement.
• Missing temporal or physical evidence remains explicitly unknown.

Source and current boundaries

Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.

Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.

Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization.

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.