LabWare sample lifecycle—first-run working review
WORKING NOTES — review decisions belong in your controlled records.
Guide: https://seal.run/integrations/labware

Use this with the LabWare sample lifecycle first-run procedure. Retain the actual configuration and evidence, then record what happened in each receiving exercise. Expected behaviour is printed as a prompt; your observed result starts blank.

1. Installed configuration and source route
Record the installed LabWare configuration, approved REST read resources, authentication method and the query used to check each outcome. Identify which system owns requests, sample IDs, collection, test assignment and review status. Retain a real request/response or export specimen.
Your evidence and observations:
[Not recorded]

2. Identity and expected population
Trace one manufacturing request to its returned sample ID and physical collection event. List expected tests and result instances. Keep request, collection, result-arrival and review timestamps separate, with their source evidence.
Your evidence and observations:
[Not recorded]

3. Quantity and receiving evidence
Record original and comparison values/units, qualifiers, preparation basis and source status mappings for each result. Compare expected tests with values received and reviews completed; list unknown statuses and missing events individually.
Your evidence and observations:
[Not recorded]

4. Exercise 1: Receive results before collection evidence
Input: Read the two result events while the collection confirmation is absent, then read COL-820 later.
Expected: The values remain linked to LW-S820. The missing collection evidence is visible until COL-820 arrives; adding it does not create another sample or another result.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

5. Exercise 2: Read the same result versions twice
Input: Read the identical GLU and LAC source result versions a second time.
Expected: The receiving view still has two scientific results and can trace both reads. The expected-test population remains two.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

6. Exercise 3: Change review state only
Input: Provide a later source observation that approves LW-R820L without changing 0.80 g/L.
Expected: The eligibility count changes from one of two to two of two. The original quantity, comparison quantity and result identity stay intact, with the review update traceable.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

7. Exercise 4: Read a qualified value or unknown status
Input: In separate test copies, replace the result text with <0.05 g/L, or use a source review code not yet in the mapping.
Expected: The qualified quantity retains its less-than meaning; any converted representation is <50 mg/L on the same basis. The unmapped status does not become Approved. Each exception identifies the affected result.
Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Your evidence and observations:
[Not recorded]

8. Implementation review and next work
Identify the configuration/mapping revision tested, reviewer, open issues and owner for each next action. Cite the retained source and destination evidence. A filled note is not itself an accepted test; record the review decision through your actual process.
Your evidence and observations:
[Not recorded]

EVIDENCE NEEDED TO FINISH
The request-to-collection relationship is supported, result conversions preserve meaning and review coverage agrees with the expected tests. Data arrival cannot stand in for collection or laboratory approval. The exchange owner can identify the exact outstanding event, result or review.