The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Restore network connectivity for office-floor switch B after the midday outage. Reboot switch-b-3,…
Execute — do the immediate task
+Restore network connectivity for office-floor switch B after the midday outage. Reboot switch-b-3, verify uplink to core-switch-1 is up, run a traceroute from app-server-4 to the internet gateway, and confirm DNS and NTP still resolve. Escalate to the network lead, Carla Jimenez, if latency remains above 50ms for any hop. Report completion by 14:30.
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 the network team, make the fault obvious. Put the RTT and packet loss for…
Improve — make it easier to accept
+Before I hand this to the network team, make the fault obvious. Put the RTT and packet loss for each hop at the top, highlight any route flaps or asymmetric paths, and flag devices with CPU over 70 percent or interface errors so a reviewer can decide whether to blame cabling, configuration, or upstream provider.
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
+At 11:50 users on floor B could not reach websites, while they still pinged internal file servers.…
Decide — diagnose the stuck moment
+Users on floor B suddenly lost external access but internal servers are reachable
At 11:50 users on floor B could not reach websites, while they still pinged internal file servers. I restarted the local switch and cleared the ARP table but the issue persisted. I don't know whether to suspect the ISP uplink, a core routing problem, or a VLAN misconfiguration. Given these symptoms, what's the most likely culprit and the step that will prove it quickly?
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 outage we run the same checklist: reboot switch, clear ARP, traceroute, then call ISP—wasting…
Become — change the pattern
+We repeatedly re-run the same network checks during outages
Every outage we run the same checklist: reboot switch, clear ARP, traceroute, then call ISP—wasting time because we rarely record which step actually fixed it. What monitoring or habit change would let us stop guessing and reach the true cause faster on the next incident?
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 operating system work people do in Linux.
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.