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 the draft audit report ready; send it to the finance director and then to the external…
Execute — do the immediate task
+I have the draft audit report ready; send it to the finance director and then to the external auditor for review, with a Friday COB deadline. Before sending, confirm the sampling methodology, findings, and corrective action plans are all documented and cross-referenced to working papers.
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 share the internal audit report with the audit committee, make it easy for non-finance…
Improve — make it easier to accept
+Before I share the internal audit report with the audit committee, make it easy for non-finance members to approve — surface the key risks and net effect on reserves up front, make the recommendations scannable, and flag any areas where evidence is thin and will draw questions.
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
+The external auditor has requested backup for a sample transaction but our working papers don't…
Decide — diagnose the stuck moment
+The auditor asked for backup that isn't clearly itemized.
The external auditor has requested backup for a sample transaction but our working papers don't clearly itemize the supporting invoices; the finance director wants the report in two days. I don't know if the missing backup is an oversight or a control gap. What should I prioritize: reconstructing the backup now, flagging the uncertainty in the report, or asking for a short extension?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Before every audit we end up chasing missing supporting documents, which delays sign-off and makes…
Become — change the pattern
+We repeatedly chase missing supporting docs before audits.
Before every audit we end up chasing missing supporting documents, which delays sign-off and makes us look sloppy. Across past audits where do we lose control — unclear document owners, poor filing conventions, or inadequate sampling notes? Recommend one habit to fix now that will cut audit chase time by half.
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.
Financial ControllerAirline Operations ControllerAviation Quality InspectorAviation Safety OfficerVat ConsultantForensic Accountantalso: Prepare financial statementsalso: Conduct financial auditsalso: Prepare budget reports
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.