The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Production needs an updated process sheet for the new polymer run. Send the attached mass-balance…
Execute — do the immediate task
+Production needs an updated process sheet for the new polymer run. Send the attached mass-balance and control sequence to Javier in process engineering and then to Anita in operations for approval, in that order, with a Wednesday go/no-go. Confirm the stoichiometry table and reactor volume cells are correct before sending.
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 send this to operations, make the yield and key constraints obvious: put overall yield…
Improve — make it easier to accept
+Before I send this to operations, make the yield and key constraints obvious: put overall yield percent at the top, make reagent consumption per tonne easy to find, and flag steps where cycle time or cooling capacity will likely cause a line stop for a shift supervisor reviewing 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
+We scaled reactor B to 2,000 liters and the final yield dropped from 88% to 79% on the first run.…
Decide — diagnose the stuck moment
+Scale-up trials showed lower yield than predicted.
We scaled reactor B to 2,000 liters and the final yield dropped from 88% to 79% on the first run. I'm the process engineer, Javier. I'm worried the sampling point is wrong or heat transfer is inadequate, but operators argue the recipe was followed. I cannot tell whether to re-run at the same scale, adjust agitation, or tighten sampling. What's the most likely cause and the best next experiment to isolate it with one more pilot run?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+In three projects this year we lost two weeks each to ambiguous scale-up failures that later traced…
Become — change the pattern
+Each scale-up repeats the same delay troubleshooting heat transfer and sampling issues.
In three projects this year we lost two weeks each to ambiguous scale-up failures that later traced to either sampling location or cooling rates. I manage scale-up. Which routine should I change to save that wasted time: mandate early thermocouple mapping in every prototype, require a standardized sampling map attached to every batch log, or run a short heat transfer trial before full runs? Pick one and say how to make it stick across teams.
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.
Chemical EngineerNlp EngineerSemiconductor EngineerThermal EngineerAnalytical Lab TechnicianBrewery Quality Technicianalso: Develop improved production processes
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.