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 clinic's finance and mailing list workbook for the pesticide outreach program. Send an…
Execute — do the immediate task
+I have the clinic's finance and mailing list workbook for the pesticide outreach program. Send an updated reconciliation table and the printed-label-ready mailing sheet to Mark in accounts payable and to Jenna in communications for tomorrow's drop, but check that every address has a postal code, confirm the budget totals match the ledger, and remove any duplicate contact rows first.
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 accounts and communications, make it approval-friendly: surface the budget…
Improve — make it easier to accept
+Before I hand this to accounts and communications, make it approval-friendly: surface the budget variance and remaining balance at the top, make the field that shows 'consent to receive materials' obvious, and flag any recipients who are outside the approved target counties or have missing postal codes that will make the mail house reject the batch.
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 prepared the payment reconciliation and mailing list but procurement stopped the payment because…
Decide — diagnose the stuck moment
+Procurement says the vendor needs a verified vendor code before payment
I prepared the payment reconciliation and mailing list but procurement stopped the payment because several vendors lack a vendor code; I don't know which vendor codes are correct, the procurement lead is in another timezone, and the drop is scheduled for Friday. Should I delay the mailing to ensure correct vendor codes, or proceed with the batch and resolve payment after delivery? What evidence will keep us safe if invoices appear later?
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 outreach cycle I end up re-cleaning addresses and reconciling tiny budget discrepancies just…
Become — change the pattern
+We keep fixing duplicate contacts and mismatched budgets at the last minute
Every outreach cycle I end up re-cleaning addresses and reconciling tiny budget discrepancies just before the mail runs, which wastes a day and strains communications and finance. What habits or spreadsheet checks should I adopt so addresses, consent flags, and budget totals validate automatically earlier in the process?
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.