The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Email the draft ecological study protocol and the species observation spreadsheet to Dr. Aisha Khan…
Execute — do the immediate task
+Email the draft ecological study protocol and the species observation spreadsheet to Dr. Aisha Khan and then to the lab safety officer, Tom Reed, asking for comments by Thursday; confirm species codes, date fields, and GPS coordinates are complete 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 circulate the field observation workbook, make it easy to use: surface the target species…
Improve — make it easier to accept
+Before I circulate the field observation workbook, make it easy to use: surface the target species list and detection thresholds on the front sheet, make the sampling dates and strata findable, and flag any data fields that would make a reviewer hesitate (ambiguous species codes, missing coordinate precision).
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
+Our field observers returned zeros for the common marsh sparrow in Sector B this week. I briefed…
Decide — diagnose the stuck moment
+Observers reported zero counts for a usually common species
Our field observers returned zeros for the common marsh sparrow in Sector B this week. I briefed Dr. Khan that we followed the protocol but she suspects a detection or recording error. I can’t redeploy observers before the next window. What is the likeliest cause of zeros in this context and the fastest corrective note to send to observers to reduce repeat errors?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We repeatedly get biologically improbable zeros or spikes in our survey spreadsheets and then spend…
Become — change the pattern
+Surveys keep yielding implausible zeros or outliers
We repeatedly get biologically improbable zeros or spikes in our survey spreadsheets and then spend days cleaning data. That wastes analyst time and weakens papers. Where are we losing quality — training, data collection forms, or validation rules — and what single change would prevent most of these bad records going forward?
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.