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 to record calibration offsets from yesterday’s field run so the lab can update the sensor…
Execute — do the immediate task
+I need to record calibration offsets from yesterday’s field run so the lab can update the sensor firmware. Put the raw timestamps and measured counts into a single sheet, apply the known temperature correction, compute the per-channel offset and flag any channels whose offset changed by more than 0.05 units. Prepare the sheet so the hardware engineer can sign off Friday and include a one-line note of method at the top.
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 calibration results to the hardware team, make it easy to verify. Show the pre- and…
Improve — make it easier to accept
+Before I send calibration results to the hardware team, make it easy to verify. Show the pre- and post-temperature-corrected traces side by side, surface the channel offsets and the three biggest outliers in a small table at the top, and attach the ambient temperature and firmware version used. Highlight any channels exceeding the 0.05 change threshold and suggest whether a re-run is needed.
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 finished a remote calibration sweep and channel 7 shows intermittent spikes; the tech insists…
Decide — diagnose the stuck moment
+Field run returned unexpected spikes on channel 7
We finished a remote calibration sweep and channel 7 shows intermittent spikes; the tech insists the cable was secure. I worry the sensor head was knocked and that overnight drift will invalidate the offsets. I cannot tell whether this is a transient or a real hardware fault. What is the likely diagnosis and the next three practical checks I should run before we report the offsets?
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 the last six calibrations we keep re-running the sweep because a handful of channels drift…
Become — change the pattern
+Repeated rework after field sweeps delays firmware updates
Over the last six calibrations we keep re-running the sweep because a handful of channels drift after transport. It eats a day each trip and frustrates the hardware engineer waiting on offsets. Which three habits in how we capture, log, and pre-screen field data should I change so fewer runs require repeat field work and firmware updates happen on schedule?
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.