3006 · Protocols and participants
Chapter 3 · Context beyond the registry
Carry an exact participant from a proposed protocol into its evidence graph without creating a new identity.
Open a workspace beside this lesson. Protected links keep their existing access gates; no new permission is granted by this course.
Why this matters
The chapter argues that identity alone does not supply workflows, semantics, provenance or authority.
An agent needs the relationship between a participant and a particular step, not just a catalogue name.
Step by step
01 Inspect the proposed run-step context
Screen or control: P3 selected step and participants tab
Why: The workflow is where an identifier acquires a specific proposed role.
How: Open the proposed run step and compare its definition GDTI with the participant IDs and exact directed assertion IDs.
What you should see: Separate step, participant and relationship addresses.
Verify: The occurrence pointer is not relabeled as a GS1 asset key.
02 Traverse and return
Screen or control: Open exact participant in P5; return to the same protocol step
Why: Continuity matters only if the receiver validates the precise references.
How: Follow one participant link, inspect its original record and incoming assertion, then return to the original step.
What you should see: Exact navigation with no name-based substitution.
Verify: The participant address and step definition match before and after navigation.
What is happening under the surface
A step definition, a participant and their directed assertion are three separate addresses.
Required role labels do not bind physical participants. A retained assertion can be inspected without being promoted to compatibility or execution permission.
Common mistakes
- Joining a participant by a similarly named record.
- Treating a source assertion as a tested or company-approved configuration.
The records an agent needs
The current public walkthrough demonstrates exact directed relationship traversal inside an authored sample. It does not run a protocol or establish a physical binding.
Exact retained identities
urn:epc:id:gdti:0614141.00105.1Anonymous package occurrence pointers
#/P3/protocolTemplates/0/ordered_steps/5#/P5/nodes#/P5/edgesFields or record paths to inspect
stepDefinitionGdtiabtidauthorityEvidencePointers locate records; hashes pin bytes; lesson numbers locate teaching material. None substitutes for an applicable assigned GS1 identity.
Apply what you learned
Record one complete step-to-participant inspection trail.
Prepare these outputs
- Step GDTI and occurrence pointer
- Participant address
- Directed assertion address
- Authority and validation gaps
Review your work against these checks
- All three records remain distinct
- The return link opens the same definition
- No proposed edge is called a verified physical bond
Check your reasoning
Why is the directed step-participant assertion needed?
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 3 · design principle. 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 demonstrated operation is read-only context traversal. Cross-system orchestration and physical action still require their own implementation, validation and authorization evidence.
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.
design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[351]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[352]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[356]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:tbl[5]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[361]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[363]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[365]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[368]design_principle
71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f/w:document/w:body/w:p[371]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.