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 have the atmospheric sensor logs and the draft data table for the research paper. Send the…
Execute — do the immediate task
+I have the atmospheric sensor logs and the draft data table for the research paper. Send the compiled dataset to Dr. Alvarez and to the lab manager for validation, signers in that order, with a Thursday deadline so the analysis can start — but first confirm sensor timestamps are in UTC and that any flagged gaps are documented.
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 Dr. Alvarez and the lab manager, make the dataset easy to validate — put UTC…
Improve — make it easier to accept
+Before I hand this to Dr. Alvarez and the lab manager, make the dataset easy to validate — put UTC timestamps in the first column, summarize missing-data windows up top, and flag any sensors whose readings drift by more than 5 percent compared with neighboring stations during the collection period.
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
+Station B12 shows a steady overnight pressure rise of 8 percent compared with all other stations…
Decide — diagnose the stuck moment
+One station's pressure readings jumped overnight; I don't know if it was sensor drift or a real event
Station B12 shows a steady overnight pressure rise of 8 percent compared with all other stations flat for the same hours. Dr. Alvarez is out in the field and wants results fast. I fear it is sensor drift, but if I discard it we lose a possible real event. What is the most likely diagnosis and the best immediate step that preserves the integrity of the paper and keeps the Thursday analysis start date?
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 several datasets we repeatedly lose days because timestamps are mixed time zones or sensors…
Become — change the pattern
+We keep losing analysis time to undocumented timestamp and drift issues
Across several datasets we repeatedly lose days because timestamps are mixed time zones or sensors drift without a documented calibration. I curate these datasets and want one habit change and one procedural tweak that would halve the time spent chasing metadata before analysis begins.
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.