The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Mark Invoice 1983 for client Oak & Row as paid. Payment was received via bank transfer for $3,400…
Execute — do the immediate task
+Mark Invoice 1983 for client Oak & Row as paid. Payment was received via bank transfer for $3,400 on July 12. Update payment status, record the payment date and method, and add a note: "Received 12 Jul, ref TRX9876." Then email a receipt to the contact Lydia Hart and cc our records inbox.
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 mark invoices as paid, make the action audit-safe: surface the bank reference and payment…
Improve — make it easier to accept
+Before I mark invoices as paid, make the action audit-safe: surface the bank reference and payment date up front, verify the amount matches an open invoice, and flag if the payment lacks a matching reference or is a partial payment so I don’t misapply funds.
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 received a bank transfer from Oak & Row that nearly matches Invoice 1983 but is $50 short. I…
Decide — diagnose the stuck moment
+I matched a transfer but the amount is slightly off.
I received a bank transfer from Oak & Row that nearly matches Invoice 1983 but is $50 short. I don’t know if it’s a partial payment, a bank fee, or a mistaken amount. I’m worried marking it paid will misreport revenue. What should I check now and what note or communication should I send to the client before I finalize the status?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep marking invoices as paid on sight of transfers and later discover mismatches, which creates…
Become — change the pattern
+We sometimes mark invoices paid without matching references and later correct them.
We keep marking invoices as paid on sight of transfers and later discover mismatches, which creates reconciliation headaches. Is the root cause poor payment instructions, lax checking, or pressure to clear accounts quickly? Recommend one strict verification step to add to our workflow that prevents misapplied payments without adding lots of extra work.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other payments work people do in PayPal.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.