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’m about to inspect the beverage fermentation room for compliance this morning. Walk through the…
Execute — do the immediate task
+I’m about to inspect the beverage fermentation room for compliance this morning. Walk through the checklist and call out any wording in the sanitation and PPE sections that could be misread by a busy technician, then suggest one-line rewrites so instructions are unmistakable during a quick walk-through.
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 inspection list to the fermentation technologist and the compliance officer,…
Improve — make it easier to accept
+Before I hand this inspection list to the fermentation technologist and the compliance officer, make it easy to act on: put the pass/fail items up front, pull the corrective-action timeframes into a single column, and flag anything that will make a reviewer hesitate about safety versus production speed.
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
+During yesterday’s floor check, Miguel the fermentation technologist pushed back that my note about…
Decide — diagnose the stuck moment
+The technician disputed a cleanliness note
During yesterday’s floor check, Miguel the fermentation technologist pushed back that my note about 'no visible residue' is unrealistic between batches. I’m worried calling it non-compliant will start a labor dispute and slow production. I cannot tell Miguel to reduce throughput. Is the likely issue my wording or the standard, and what’s the best next step to resolve inspection disagreement without escalating?
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 week an inspection note becomes a production stoppage because staff interpret sanitation…
Become — change the pattern
+Inspections keep causing production delays
Every week an inspection note becomes a production stoppage because staff interpret sanitation language as requiring full shutdowns. Where are we repeatedly creating operational friction in our checklists, and what one change to inspection language or timing would reduce false positives and keep production moving?
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.