The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Tomorrow's production forecast just rose by 30% for a retailer order. Send the updated work…
Execute — do the immediate task
+Tomorrow's production forecast just rose by 30% for a retailer order. Send the updated work allocation and machine schedule to Priya in production planning and to Marco, the shift supervisor, for signoff, signers in that order, with a Friday deadline — confirm oven capacity and spare parts on the sheet before sending.
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 send this to operations, make the allocation clear to approve — put total required labor…
Improve — make it easier to accept
+Before I send this to operations, make the allocation clear to approve — put total required labor and machine hours at the top, highlight any overtime needed, show which product batches push beyond capacity, and flag what would make Marco hesitate (no spare operator, missing critical ingredient).
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
+The planner bumped production and one line is scheduled at 110% capacity next week. I can split…
Decide — diagnose the stuck moment
+A key line is at 110% capacity for next week.
The planner bumped production and one line is scheduled at 110% capacity next week. I can split runs across shifts, subcontract part of the order, or ask the customer to accept later delivery. I don't know the customer's flexibility on date, subcontractor cost, or operator availability for extra shifts. Which option preserves on‑time delivery and credibility with least operational risk?
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 promising deliveries before validating line capacity, then scramble with overtime or…
Become — change the pattern
+We routinely overcommit because capacity checks happen after orders are accepted.
We keep promising deliveries before validating line capacity, then scramble with overtime or subcontracting that eats margin. Which habit should I change in that ordering process, and what simple pre‑acceptance check will stop chronic overcommitment without blocking real sales?
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.