The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Compile this week's incident report log and send it to Carla in Safety and to Marcus the prevention…
Execute — do the immediate task
+Compile this week's incident report log and send it to Carla in Safety and to Marcus the prevention lead for review, with Marcus signing off after Carla by Thursday. Make sure each incident has a root-cause field filled, assigned corrective actions with owners and dates, and that any high-risk items are highlighted.
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 the incident log to Safety, make it action-ready: bring the open high-risk incidents…
Improve — make it easier to accept
+Before I send the incident log to Safety, make it action-ready: bring the open high-risk incidents to the top, show the overdue corrective actions in red, and call out which incidents lack a clear root cause so Carla and Marcus can prioritize prevention work.
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
+Marcus reported that an action was marked assigned in the log but the site supervisor insists the…
Decide — diagnose the stuck moment
+Marcus says a corrective action is assigned but nothing changed on site
Marcus reported that an action was marked assigned in the log but the site supervisor insists the fix never happened. Carla wants an update by Thursday and I don't want them escalating. I only have the entry and a vague contractor note. What's the most likely break and the quickest credible way to verify and update the log?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over months we keep logging incidents as closed but they reoccur within weeks because fixes weren't…
Become — change the pattern
+We repeatedly close incidents on paper but they recur in weeks
Over months we keep logging incidents as closed but they reoccur within weeks because fixes weren't implemented or monitored. What single reporting habit will stop cosmetic closures and ensure corrective actions are actually completed and sustained?
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.