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 a clean irregularities report for the audit team by Wednesday. Run the transaction sheet…
Execute — do the immediate task
+I need a clean irregularities report for the audit team by Wednesday. Run the transaction sheet against vendor master changes and flag any entries where vendor name or bank details changed, amounts are outside usual ranges, or duplicate invoice numbers appear. Send the flagged list to Nora in Internal Audit first and to Raj in Legal second for their quick read, and keep a copy in the secure folder with a one-line note of why each was flagged.
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 Internal Audit, make it easy for them to find real problems: surface the…
Improve — make it easier to accept
+Before I hand this to Internal Audit, make it easy for them to find real problems: surface the high-risk flags at the top, add a column explaining why each transaction was flagged (name change, bank change, outlier amount, duplicate invoice), include the prior three months’ averages for comparison, and mark which ones need immediate freeze or vendor contact. Don’t bury duplicates in raw data.
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 pulled the vendor ledger and discovered five transactions sharing an invoice number with…
Decide — diagnose the stuck moment
+I found several transactions with the same invoice number but different amounts.
I pulled the vendor ledger and discovered five transactions sharing an invoice number with mismatched amounts; Nora in Audit will want fraud, Raj in Legal will want evidence. I don’t know if this was a data-entry duplication, a valid credit application, or something malicious. What is the most likely diagnosis and the immediate next action I should take to establish whether this is error or fraud?
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 quarter we rerun vendor exception lists and waste time re-investigating the same false…
Become — change the pattern
+We keep reopening vendor exceptions every quarter.
Every quarter we rerun vendor exception lists and waste time re-investigating the same false positives: bank-format changes, benign name abbreviations, and routine volume bursts. It undermines Audit’s trust and drains me. Which two process changes would reduce recurring noise and how do I implement them this month so future exception reports show fewer false positives?
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.