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 evidence for the compliance review. Pull historical transaction records and supporting…
Execute — do the immediate task
+I need evidence for the compliance review. Pull historical transaction records and supporting invoices for account 4200 from January through June, summarize exceptions, and deliver the bundle to Marco, the audit manager, and Leila in compliance by Wednesday afternoon; verify every file is legible and matches the ledger amounts 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 hand the historical data to Leila, make it easier for her to judge exceptions: create a…
Improve — make it easier to accept
+Before I hand the historical data to Leila, make it easier for her to judge exceptions: create a single pivot that shows monthly totals, highlight months with variance over five percent, attach a one-paragraph explanation for each exception, and include links to the scanned invoices so she can click straight to evidence.
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
+While pulling invoices for account 4200, I discovered nine invoices that don’t match ledger totals…
Decide — diagnose the stuck moment
+I found mismatched invoices across years.
While pulling invoices for account 4200, I discovered nine invoices that don’t match ledger totals across 2019–2021. I’m responsible for the evidence bundle but I don’t know whether these are posting errors, duplicate entries, or misfiled scans. What diagnostics should I run first to identify the root cause and what should I tell Marco so he isn’t blindsided at the review?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every audit season we re-run the same searches and re-check archival invoices, wasting two weeks…
Become — change the pattern
+Each audit we scramble to assemble the same old paperwork.
Every audit season we re-run the same searches and re-check archival invoices, wasting two weeks per audit and straining the team. Where are we losing time in researching historical data and what single archival practice or naming convention could stop us repeating the same hunt each year?
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.
Field ResearcherHistorianMilitary HistorianDevelopment ResearcherEconomic HistorianOral Historianalso: Analyze and interpret historical dataalso: Do historical research
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.