The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need the test run record moved into the official procedure log and signed off. Put the entry for…
Execute — do the immediate task
+I need the test run record moved into the official procedure log and signed off. Put the entry for July 14, 2026 at the top, include tester Maria Gonzales, specimen ID 78421, instruments used (LC‑MS model A7), calibration lot 19B, pass/fail for each step, and a notes cell for deviations. Before I send it to Dr. Reed for approval on Friday, check every timestamp and that the totals for reagent volume recalc correctly.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before this goes into the lab archive, make the procedure sheet easy to audit. Surface the final…
Improve — make it easier to accept
+Before this goes into the lab archive, make the procedure sheet easy to audit. Surface the final pass/fail outcome and deviation count at the top, make instrument calibration details findable on the left, and flag any rows where operator or lot numbers are missing or where elapsed time deviates more than 10% from the SOP.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I was reviewing Maria's run and one step shows completed at 09:12 while the previous step is 09:18.…
Decide — diagnose the stuck moment
+Technician logged one step as complete but timestamp is earlier than the previous step
I was reviewing Maria's run and one step shows completed at 09:12 while the previous step is 09:18. I can't tell if she mis‑typed a timestamp, copied the wrong SOP line, or the instrument clock was off. Dr. Reed will want an explanation. What is the most likely cause and the next action: correct the timestamp with a note, lock the row and ask Maria to confirm, or rerun the critical step now?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across five recent runs, calibration lot and instrument serial number are often blank and we lose…
Become — change the pattern
+We repeatedly get incomplete calibration details on procedure logs
Across five recent runs, calibration lot and instrument serial number are often blank and we lose time chasing techs for that data. Each missing entry delays signoff by a day and risks failing external audit. What simple habit or sheet change will force calibration details to appear at data entry and cut follow‑up work by half?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Where the evidence lives
Who was seen doing this, and what people really ask.
Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.