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 have raw instrument readouts and reagent batch numbers for a set of samples. Send the…
Execute — do the immediate task
+I have raw instrument readouts and reagent batch numbers for a set of samples. Send the analyzed-results workbook to Dr. Patel in the lab and to the safety officer for sign-off, with a two-business-day deadline — but first ensure every sample row links to the correct reagent batch and dilution factor.
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 I hand this to Dr. Patel, make the results easier to verify. Pull the reagent-batch and…
Improve — make it easier to accept
+Before I hand this to Dr. Patel, make the results easier to verify. Pull the reagent-batch and dilution columns into the top of the result view, add a column that flags any sample where the signal-to-noise ratio is below two, and mark any sample that lacks an instrument ID so the safety officer can question its provenance quickly.
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 joined the instrument export with the sample-tracking sheet and one row now shows a blank batch…
Decide — diagnose the stuck moment
+One sample lost its batch number during a join.
I joined the instrument export with the sample-tracking sheet and one row now shows a blank batch number; Dr. Patel will assume the measurement is unusable and safety will delay approval. I don’t know if the blank came from a misspelled sample ID or from duplicate IDs collapsing in the join. What is the most likely cause and the best immediate step to restore the correct batch link?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep losing lab hours because merged exports regularly drop reagent-batch or instrument IDs,…
Become — change the pattern
+We repeatedly have missing provenance after merges.
We keep losing lab hours because merged exports regularly drop reagent-batch or instrument IDs, forcing manual tracebacks and delaying sign-off. Where are we most likely introducing these provenance gaps and what one habit — naming convention, pre-merge check, or lock on the sample-tracking sheet — should I adopt to stop it?
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.
Agricultural ChemistAnalytical ChemistApi Manufacturing ChemistCosmetic ChemistEnvironmental ChemistForensic Chemistalso: Analyze biological substances like DNA and proteins
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.