The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The excavation logs and context register need to be reviewed and then sent to the site director and…
Execute — do the immediate task
+The excavation logs and context register need to be reviewed and then sent to the site director and the archive curator for sign-off by Friday. Check that every context has date, depth, finder, and linked photograph reference, confirm the stratigraphy sheet recalculates total depths when new contexts are added, then email the complete workbook to Tom at field operations and to Dr. Evans in the archive in that order with a Friday deadline.
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 the site director, make the context register easy to approve: put the…
Improve — make it easier to accept
+Before I hand this to the site director, make the context register easy to approve: put the high-level site summary and most likely dating at the top, make the finds count and conservation flags immediately visible, and flag any contexts that lack photo or section drawings that 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
+I merged trench logs from two teams and now context 112 has no photo and the site director suspects…
Decide — diagnose the stuck moment
+An important context lost its photograph link during a merge.
I merged trench logs from two teams and now context 112 has no photo and the site director suspects it was overwritten. I’m not sure if I misaligned rows, changed the photo ID column header, or swapped which folder we point to. What is the likeliest cause and the quickest set of checks to recover or prove the photograph linkage before Tom asks?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+After several seasons I still spend days fixing mismatched context IDs and missing photo links…
Become — change the pattern
+Repeatedly fixing inconsistent context IDs and photo references across season files.
After several seasons I still spend days fixing mismatched context IDs and missing photo links between field packets and the archive. Which file convention or brief pre-upload checklist will stop these recurring errors so the archive curator trusts the dataset and I stop doing last-minute rescues?
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.