The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Complete the transaction testing sample for the audit and deliver the workbook to Karen on Internal…
Execute — do the immediate task
+Complete the transaction testing sample for the audit and deliver the workbook to Karen on Internal Audit and then to Raj in Compliance for sign-off, reviewers in that order, by Thursday. Before delivery, confirm that the sampling sheet matches the source transactions and that each tested entry links to a scanned supporting document.
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 transaction test file to Karen on Internal Audit, make it easy to approve: put…
Improve — make it easier to accept
+Before I hand this transaction test file to Karen on Internal Audit, make it easy to approve: put the sampling methodology and error thresholds on the first tab, highlight any exception transactions and why they failed, and include direct hyperlinks to the underlying scans so an auditor can verify in two clicks.
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
+During transaction testing I found a cluster of exceptions under supplier code 4512; Karen needs a…
Decide — diagnose the stuck moment
+My sample shows an unexpected cluster of exceptions in one supplier code
During transaction testing I found a cluster of exceptions under supplier code 4512; Karen needs a root cause and Raj will expect corrective action. I don't know if this is a misclassified coding, duplicate payments, or a bank error. What tests should I run first to narrow the cause quickly?
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 I rebuild sampling sheets, re-link hundreds of scans and re-run the same tests,…
Become — change the pattern
+Each audit cycle I re-create sampling and linking work from scratch
Every audit season I rebuild sampling sheets, re-link hundreds of scans and re-run the same tests, which burns days and invites inconsistencies. What procedural habit or small template change will save time and make our transaction testing repeatable and defensible?
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.