Inspect one exact node inside the complete graph

Why this matters

P5 makes all other pillars addressable to agents.

A readable node card is only the entry to the record and its provenance, not a replacement for them.

Step by step

1. 01

   Open an exact component record

   Screen or control: Exact CPI graph link

   Why: The lesson should begin with a known address rather than a name search.

   How: Open the CPI graph link. Read Same object. Exact context, incoming P2 occurrence and the selected inspector.

   What you should see: The selected node is urn:epc:id:cpi:0614141.414141.41, linked from #/P2/modules/1.

   Verify: Verify Exact source ID and Source occurrence pointer#/P5/nodes/3; do not interpret the source pointer as a new EPC identity.

2. 02

   Inspect fields rather than labels

   Screen or control: Exact graph record inspector

   Why: A title alone does not expose assignment, evidence or authority.

   How: Read reference kind, state, source, evidence locator, asserting actor, authority evidence, assertion time and scope. Scroll within the inspector if needed.

   What you should see: The record remains demo_non_issued and fictional authored; missing actor/authority/time values stay Unknown.

   Verify: Do not manufacture a timestamp or actor for a node whose source object lacks those fields.

3. 03

   Open the original node JSON

   Screen or control: Inspect exact JSON

   Why: Machine consumers need original structured fields, not only human summaries.

   How: Select Inspect exact JSON and read id, identity, referenceKind, evidence and authorityState.

   What you should see: The JSON is the original selected node object, not a newly edited interpretation.

   Verify: Compare its exact id with the selected address. Record null/unknown fields as supplied rather than filling them from neighboring edges.

4. 04

   Restore the complete model

   Screen or control: Show complete graph · Fit view

   Why: A focused subset must not become hidden data loss.

   How: Choose Show complete graph, then Fit view. Compare visible counts with the complete model.

   What you should see: The full 329-node/231-relationship view is restored; selection/focus is cleared.

   Verify: The full graph JSON remains unchanged before and after inspection. No source node is deleted by closing the inspector.

What is happening under the surface

The complete public graph contains 329 nodes and 231 directed relationships, retained from the same pinned package.

A focused URL selects an existing exact node and its direct-neighbor viewport; the full graph remains available.

id, identity and source occurrence pointer are different fields. The sample node has authored evidence, non-issued state and unknown authority.

Common mistakes

• A missing node actor cannot be inferred from a related relationship’s actor.
• Unknown authority is not a grant of permission.
• Zoom, fit and closing an inspector do not alter the source model.

The records an agent needs

The selected graph record, P2 source occurrence and asserted EPC identity are preserved separately. Focus is a visual direct-neighbor projection over original records; source counts and JSON remain complete.

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

Apply what you learned

Produce an exact node-inspection receipt before and after restoring the complete graph.

Prepare these outputs

• Node ID, source pointer, reference kind and assignment state.
• Evidence locator and explicit unknown authority/time fields.
• Focused and complete counts with a note that the original JSON is unchanged.

Review your work against these checks

• The exact original CPI remains addressable.
• No field is invented from labels or nearby records.
• The complete graph restores 329/231.

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.