Open the exact participant and role behind a step

Why this matters

Role labels alone do not establish an identity binding.

Exact cross-pillar continuity lets an agent inspect the referenced unit/context and its assertion provenance.

Step by step

1. 01

   Open the intended step

   Screen or control: Select exact step 6 in P3 · Participants & materials

   Why: Different steps reference different participants.

   How: Open the exact step 6 screen link and select Participants & materials. Read both the role chips and Exact participant & service-role assertions.

   What you should see: The selected procedure occurrence is #/P3/protocolTemplates/0/ordered_steps/5.

   Verify: Do not use a similarly named card from another step as a substitute.

2. 02

   Inspect the exact cycler assertion

   Screen or control: Thermal cycler asset in the exact participant list

   Why: The participant node and the step-participant assertion are separate objects.

   How: Select the exact cycler entry. Read Same object. Exact context in P5 and the incoming source occurrence and directed assertion ID.

   What you should see: The target node is urn:epc:id:giai:0614141.4; via is urn:epc:id:gdti:0614141.00900.190.

   Verify: Record #/P5/edges/189 and verify a is the selected step GDTI and b is the exact cycler GIAI.

3. 03

   Inspect service roles without granting permission

   Screen or control: Return to the same protocol step · Operator service relationship

   Why: A service role must remain distinct from the physical asset and authorization.

   How: Return to step 6, reopen Participants & materials and select the operator service relationship. Inspect its exact GSRN and authored relationships.

   What you should see: The operator node is urn:epc:id:gsrn:0614141.4343434343; its record does not establish employment or execution permission.

   Verify: Read unknown authority and null/unknown time. Do not translate “referenced” into “authorized”.

4. 04

   Verify reversible continuity

   Screen or control: Return to the same protocol step

   Why: A drill-down should preserve the original learning context.

   How: Use the P5 return link. Confirm the selected step title and source occurrence before opening another participant.

   What you should see: P3 selects the original exact step definition rather than its first/default step.

   Verify: Compare the before/after GDTI and pointer. The tab may return to its default Procedure & evidence; re-open Participants & materials explicitly.

What is happening under the surface

componentRoles and bomRolesUsed are retained teaching labels; the exact participant list is derived only from directed references-step-participant graph assertions.

The selected run-step list includes a cycler GIAI, component CPIs, material SGTINs and separate operator/configuration-agent GSRNs.

The link carries node, from and via. The receiver verifies the exact step pointer and directed relationship instead of matching a name.

Common mistakes

• A role chip cannot by itself resolve an exact asset.
• Do not infer compatibility, installation, ownership or permission from a step-participant reference.
• The return link restores the exact definition, not every transient tab or scroll setting.

The records an agent needs

The query is a navigation request, not an identity assertion. Only an existing directed step-to-participant edge qualifies. Unknown parameters, mismatched endpoints and other source lanes are rejected within this public model.

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

Apply what you learned

Trace one physical participant and one service role from step 6 to P5 and back.

Prepare these outputs

• Two target IDs, exact from pointer and via relationship IDs.
• Original edge endpoint/provenance fields.
• A return-check screenshot showing the exact step selected.

Review your work against these checks

• Both target nodes come from retained directed assertions.
• No join is based on a label.
• The original step GDTI remains the return address.

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.