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 14 new survey runs with raw point logs and photos that must join the master survey history.…
Execute — do the immediate task
+I have 14 new survey runs with raw point logs and photos that must join the master survey history. Import the new sheets, append metadata, and share the consolidated record with Tomas in archives and with Leah the survey lead for verification, due Monday 10am. Before sharing, ensure each run has a complete audit trail and photos are linked to the correct point IDs.
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 publish the updated survey history, make it easy for Tomas to accept it: present missing…
Improve — make it easier to accept
+Before I publish the updated survey history, make it easy for Tomas to accept it: present missing metadata in a top table, make the latest revision date and editor visible, and flag any runs where photos don't match point IDs or where the audit trail would make a reviewer hesitate.
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
+After importing fourteen runs, several point logs lack timestamps and Tomas will reject the batch.…
Decide — diagnose the stuck moment
+Some runs show missing timestamps after import
After importing fourteen runs, several point logs lack timestamps and Tomas will reject the batch. I don't know if the timestamps were lost in the export or never recorded on site. What checks prove which happened, and what's the least disruptive repair so Leah can accept the master record?
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 projects we repeatedly rebuild audit trails, relink photos, and normalize revision histories…
Become — change the pattern
+We keep repairing broken audit links across projects
Across projects we repeatedly rebuild audit trails, relink photos, and normalize revision histories because field teams export inconsistent packages. Recommend one change to how teams submit runs that would stop this recurring rework and restore trust in the master survey record.
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.
Drone Mapping PilotParametric Design SpecialistSurveyorMarine BiologistPharma Formulation Scientistalso: Maintain detailed records of observations
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.