Read the ordered method without claiming a run

Why this matters

A workflow needs ordered, addressable steps rather than an unstructured paragraph.

A human-friendly diagram is a projection of retained definitions and directed relationships.

Step by step

1. 01

   Read the complete sequence

   Screen or control: Choose the retained protocol · Show every step

   Why: The full sequence is needed before inspecting one participant.

   How: Open P3. Read all eight step cards from Identify & scope to Package results & provenance. If the track is compact, choose Show every step.

   What you should see: All eight definitions remain available in their original ordinal order.

   Verify: Record ordinals1,6 and 8 with their titles; do not treat diagram position as a new ordering assertion.

2. 02

   Inspect the selected definition

   Screen or control: Propose the PCR run · Procedure & evidence

   Why: A step title must be anchored to the exact definition.

   How: Select Propose the PCR run and read its retained procedure, step GDTI and evidence locator.

   What you should see: The selected definition is urn:epc:id:gdti:0614141.00105.1; the procedure explicitly says no instrument command is dispatched and no amplification result is generated.

   Verify: Record #/P3/protocolTemplates/0/ordered_steps/5, not /6: source arrays are zero-indexed while the displayed ordinal is 6.

3. 03

   Change the view, not the method

   Screen or control: Compact flow · Show every step

   Why: UI convenience must not silently remove or reorder source definitions.

   How: Toggle Compact flow and inspect the step-track behavior, then restore Show every step.

   What you should see: The same eight source definitions and original order remain; only presentation changes.

   Verify: Re-select step 6 and confirm its GDTI and procedure are unchanged.

4. 04

   Inspect order as a typed assertion

   Screen or control: Open selected step in P5 · Original direct relationships

   Why: Explicit graph relationships make ordering inspectable to agents.

   How: Open the exact selected step in P5 and inspect a precedes-step relationship to an adjacent definition.

   What you should see: Both step endpoints and the relationship ID remain distinct authored records.

   Verify: Read original a, b and t fields in exact JSON; a visible arrow is not evidence that either step ran.

What is happening under the surface

The one retained protocol template is Illustrative PCR composition, with eight ordered_steps and ordinal 1–8.

Each step has a distinct stepDefinitionGdti, procedureDetail and evidence locator.

The public P3 page is read-only. Compact flow changes presentation; it does not reorder definitions, add steps or execute them.

Common mistakes

• Displayed ordinal 6 is source-array index 5.
• Compact flow is not protocol reordering.
• The phrase Propose the PCR run describes a request design, not observed amplification or execution.

The records an agent needs

Step definitions are documents, not run events. The displayed step 5→step 6 edge is index 187 and step 6→step 7 edge index 205 in this pinned graph; indices are zero-based source locations, while relationship GDTIs remain the exact addresses.

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 order-and-definition receipt for three adjacent steps.

Prepare these outputs

• Displayed ordinal, exact step GDTI and zero-based source pointer for each.
• Two exact directed precedes-step edges.
• A screenshot pair before/after presentation toggle.

Review your work against these checks

• The order and source identities remain unchanged.
• Definition and execution-event roles are separated.
• No scientific run or approval is claimed.

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.