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 lab result sheets and method validation tabs that need approval. Send the validated results…
Execute — do the immediate task
+I have lab result sheets and method validation tabs that need approval. Send the validated results to Priya in procurement and then to Miguel in finance for signatures, with Friday as the deadline — but first ensure every assay has acceptance criteria met, reference samples are logged, and the chain-of-custody sheet is attached.
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 forward the analytic report to procurement, make it easy to approve: surface the pass/fail…
Improve — make it easier to accept
+Before I forward the analytic report to procurement, make it easy to approve: surface the pass/fail summary up front, bring failed tests into a single clearly labeled section, provide the methods used and control results, and flag anything that would make a reviewer hesitate like out-of-spec controls or missing raw data.
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 ran the batch and compiled the report but a routine control failed on re-check, and Priya expects…
Decide — diagnose the stuck moment
+a control sample failed after I compiled the report.
I ran the batch and compiled the report but a routine control failed on re-check, and Priya expects signed results Friday. The rest of the data looks clean but I can't tell if the failure invalidates the batch. I don't know whether to rerun, quarantine results, or disclose now. What's the likely correct step and the fastest way to present the situation so procurement and finance can decide?
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 getting approvals delayed because validation failures surface late, forcing reruns and…
Become — change the pattern
+last-minute invalidated assays delay approvals
We keep getting approvals delayed because validation failures surface late, forcing reruns and holding up procurement sign-off. That creates backlog and burns analyst overtime. What habit should I change in scheduling checks, documentation or run protocols so validation issues surface earlier and approvals stop slipping?
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.