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 a standard operating summary for a chemistry lab that handles preparation and mixing of…
Execute — do the immediate task
+I need a standard operating summary for a chemistry lab that handles preparation and mixing of compounds: safety checks, reagent quality, mixing orders, temperature and pH controls, waste handling, and a final verification sign-off for the lab manager. Keep it to one page for the hood and include a short preflight checklist for each run.
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 pin this SOP summary in the hood, make it usable during a busy run — put the critical…
Improve — make it easier to accept
+Before I pin this SOP summary in the hood, make it usable during a busy run — put the critical safety steps and the order of operations at the top, make the preflight checklist actionable (three to five items), and flag any language that sounds permissive and needs tightening to meet our QA standards.
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
+A junior technician followed our summary and still mixed a batch out of sequence. I have the…
Decide — diagnose the stuck moment
+A junior tech mixed a batch out of sequence and we lost a run.
A junior technician followed our summary and still mixed a batch out of sequence. I have the one-page summary and the tech’s notes. Which lines failed to instruct clearly, which steps need mandatory checkpoints, and what immediate correction to the summary and the trainee checklist will prevent the same mistake tomorrow?
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 repeatedly lose runs because technicians perform mixing steps out of order. Is the root cause…
Become — change the pattern
+We keep losing runs because steps are done out of order.
We repeatedly lose runs because technicians perform mixing steps out of order. Is the root cause our one-page summaries that compress procedure, inadequate in-line fail-safes, or insufficient onboarding? Recommend three concrete habit changes in documentation and training that will reduce out-of-sequence errors and preserve batch integrity.
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.