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 the confidentiality policy updated and sent to the staff list by Friday. Merge the new…
Execute — do the immediate task
+I need the confidentiality policy updated and sent to the staff list by Friday. Merge the new consent language from Legal into the existing policy, password-protect the PDF, attach the staff acknowledgment form, and confirm that printing is disabled on the PDF before you distribute.
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 circulate the confidentiality memo, make it easy for staff to comply — put the required…
Improve — make it easier to accept
+Before I circulate the confidentiality memo, make it easy for staff to comply — put the required actions up front, add a one-paragraph how-to for secure file sharing, highlight three common mistakes that trigger breaches, and flag any places where current workflows conflict with the policy.
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
+A coordinator accidentally emailed an unencrypted client file to an external vendor. Legal wants a…
Decide — diagnose the stuck moment
+Someone emailed a client file unencrypted to a vendor by mistake.
A coordinator accidentally emailed an unencrypted client file to an external vendor. Legal wants a neutral incident memo; staff need clear steps to prevent repeats. I’m unsure how much detail to include without blaming the coordinator or alarming clients. What should the immediate staff message say, what corrective actions should be required, and how do we phrase it for client notification if needed?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Small confidentiality lapses keep popping up because sharing rules aren’t practical for daily work.…
Become — change the pattern
+We keep having small confidentiality breaches due to unclear sharing rules.
Small confidentiality lapses keep popping up because sharing rules aren’t practical for daily work. Each fix becomes a new exception. Where are we losing control — the policy language, the tools, or training — and what three habits or system changes will actually reduce breaches without grinding operations to a halt?
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.