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 to record test readings for the client’s electrical panel inspection and send the worksheet…
Execute — do the immediate task
+I need to record test readings for the client’s electrical panel inspection and send the worksheet to Steve in facilities for signature by Friday — check every formula so the pass/fail and clearance values are correct before I circulate.
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 test log to Procurement, surface the fail counts and any out-of-spec voltages up…
Improve — make it easier to accept
+Before I hand this test log to Procurement, surface the fail counts and any out-of-spec voltages up top, make timestamps and device IDs easy to scan, and flag any missing manufacturer serials or calibration certificates that would make an engineer push back.
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 just finished capturing test voltages for 42 outlets in Building B; Markus the electrical lead…
Decide — diagnose the stuck moment
+I ran a batch of device tests and some voltages look high.
I just finished capturing test voltages for 42 outlets in Building B; Markus the electrical lead says three should never read above 230V but two readings are 245V and 248V. I’m afraid this is a measurement error from the handheld meter or a data-entry swap, and I cannot tell whether to mark the circuits failed or to rerun calibration. What’s the likely cause and the best immediate step to resolve with minimal rework?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across the last six inspections we keep rebuilding the same pass/fail logic and rechecking device…
Become — change the pattern
+Test logs require repeated manual recalculation and rechecks.
Across the last six inspections we keep rebuilding the same pass/fail logic and rechecking device serials, which wastes an hour per report and risks missing a bad device. Which routine should I change so tests are recorded once, automations verify thresholds, and a checklist forces serial and calibration capture before sign-off?
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.
Electronics Technician ObservatoryArchitectural TechnologistBattery Pack TechnicianEv Charging TechnicianGarment TechnologistPaint Technologistalso: Aid in operation of electrical devices and facilitiesalso: Test electrical equipment
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.