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 a full activity history for the folder Contracts/2026/Acme to answer procurement’s audit.…
Execute — do the immediate task
+I need a full activity history for the folder Contracts/2026/Acme to answer procurement’s audit. Show who viewed, edited, commented, moved, or shared files in that folder over the past 90 days, with timestamps and the IP or location if available, and export it to a CSV for the legal team.
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 legal, summarize the activity so a reviewer who dislikes raw logs can act:…
Improve — make it easier to accept
+Before I hand this to legal, summarize the activity so a reviewer who dislikes raw logs can act: surface unusual events at the top (large downloads, shares outside the company, or deletes), mark repeated failed sign-in attempts, and highlight which user made policy-changing actions in the last 30 days.
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
+Legal just asked for activity logs for the Acme contract folder and I see spikes of downloads last…
Decide — diagnose the stuck moment
+Legal requested audit logs and I’m worried about suspicious access I didn’t notice
Legal just asked for activity logs for the Acme contract folder and I see spikes of downloads last week that I don’t recognize. I’m afraid those were unauthorized or the result of a mis-shared link. I don’t know which accounts or shared links caused the spike. What’s the most likely diagnosis and the immediate steps to contain risk before legal digs deeper?
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 repeatedly get audit requests because files have strange download spikes or unexpected external…
Become — change the pattern
+We repeatedly get surprised by odd file activity in client folders
We repeatedly get audit requests because files have strange download spikes or unexpected external shares, which repeatedly rattles clients. Is the root cause usually over-permissive sharing, weak link expiry practices, or poor onboarding of new contractors? What single policy or checklist would prevent these recurrent surprises?
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 file storage work people do in Google Drive.
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.