3008 · Identity and context

Chapter 5 · Design, model and physical unit

Plan a design-to-unit evidence chain while keeping a design proposal distinct from manufacture.

Physical unit and installed-context roles Separate component context

Open a workspace beside this lesson. Protected links keep their existing access gates; no new permission is granted by this course.

Why this matters

A design describes a family or intended construction; a physical unit has its own identity and observation history.

The chapter’s birth-certificate metaphor encourages provenance from design onward, but manufacture cannot be inferred from a drawing.

Step by step

01
Draw a design-to-unit record map
Screen or control: Chapter 5 design and manufacture discussion
Why: Lifecycle continuity must not flatten a model into its units.
How: Sketch an anonymous design revision, a model description, two prospective units and one component role. Mark every link as a proposal until supported.
What you should see: Distinct design, model, unit and role records.
Verify: Two units never share a single substituted model identity.
02
Compare asset and installed context
Screen or control: P1 GIAI/CPI controls and P5 sensor view
Why: A component’s source identity survives an installed-context role.
How: Inspect the GIAI role and the supplied CPI context. Locate the original supplier-asset relationship and record its unknown physical verification.
What you should see: A preserved source identity and separate context.
Verify: No design-stage proposal is described as issued or installed.

What is happening under the surface

Retain the design document, its revision, intended model, candidate unit and component-role records separately.

A commissioning or first-observation event is a later record with its own actor, time and evidence. The current walkthrough has no CAD or manufacture receipt.

Common mistakes

Using the book’s genetic analogy to merge design, model and unit identity.
Inventing manufacture dates or treating a first observed startup as the first-ever startup.

The records an agent needs

The sample demonstrates record distinctions. CAD files, manufacturing events and exact physical-unit verification are absent and must remain explicitly absent.

Exact retained identities

urn:epc:id:giai:0614141.4urn:epc:id:cpi:0614141.414141.41

Anonymous package occurrence pointers

#/P1/demo_giai#/P1/demo_cpi#/P2/modules#/P5/edges

Fields or record paths to inspect

physicalUnitVerificationstateauthorityEvidenceassertionTime

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

Apply what you learned

Specify an evidence chain for two units built from one proposed design.

Prepare these outputs

Design/model/unit diagram
Manufacture-event evidence requirements
Component origin/context distinction

Review your work against these checks

Both units remain individually addressable
Missing dates stay unknown
No CAD or manufacture integration is claimed

Check your reasoning

Two units share a design. Which record may safely be shared?

This answer stays in page memory, is cleared when you leave, and is not sent or recorded as certification, validation or authority.

Source and current boundaries

Chapter 5 · 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.

CAD integration, manufacture, commissioning and lifecycle timestamps are future requirements, not implemented proof from this fixture.

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.