The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Send the soil and crop monitoring workbook to Priya in agronomy and to Luis, the field manager, for…
Execute — do the immediate task
+Send the soil and crop monitoring workbook to Priya in agronomy and to Luis, the field manager, for sign-off, in that order, with a Friday close. Before sending, verify the sensor data imports into the latest daily sheet, ensure the NDVI chart shows the last two weeks, and confirm conditional alerts flag fields 3B and 7A.
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 field operations, make the workbook easy to act on: put critical alerts and a…
Improve — make it easier to accept
+Before I hand this to field operations, make the workbook easy to act on: put critical alerts and a one-line recommendation for each field on the dashboard, make soil moisture and NDVI trends findable within two clicks, and highlight any calibration gaps that would make a farm manager hesitate to trust the numbers.
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
+The agronomy team says irrigation was automated; the field manager says no irrigation ran. The…
Decide — diagnose the stuck moment
+Field sensors show a sudden drop in moisture for blocks 3B and 7A.
The agronomy team says irrigation was automated; the field manager says no irrigation ran. The sensor time series shows a step change at 03:00 but the logger reports no comms errors. I cannot tell whether the sensors failed, irrigation control failed, or a real leak happened. What is the likely diagnosis and the immediate next check I should ask Luis to perform before we alert the growers?
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 the last six monitoring cycles we waste hours reconciling sensor drops and filling gaps…
Become — change the pattern
+We repeatedly chase sensor anomalies and re-run cleaning scripts before every planning meeting.
Across the last six monitoring cycles we waste hours reconciling sensor drops and filling gaps manually. Where am I losing time and risking wrong recommendations, and what one change in data validation or reporting would cut that work out of the routine?
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.