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 this server installed and booted for tomorrow's database migration. Install the operating…
Execute — do the immediate task
+I need this server installed and booted for tomorrow's database migration. Install the operating system on the new Dell R650 in rack 12U, set the root password to my personal admin pass, enable SSH for the ops team, create a local 'ops' group with sudo privileges, and leave a single unpartitioned 100 GB LVM volume for data. Verify network comes up and confirm by SSHing in from my laptop.
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 machine to the DB team, make the installer output easy to audit: surface disk…
Improve — make it easier to accept
+Before I hand this machine to the DB team, make the installer output easy to audit: surface disk layout and LVM choices at the top, show the enabled services and SSH key fingerprints, call out any nondefault security settings, and flag any steps that will require a reboot or break remote access so I can approve quickly.
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 kicked off an unattended install on the Dell R650 and after the partitioning stage I can no…
Decide — diagnose the stuck moment
+I started the installer and lost SSH after partitioning
I kicked off an unattended install on the Dell R650 and after the partitioning stage I can no longer SSH to the IP allocated by DHCP. The rack tech says the server shows the installer console locally. I don't know if the network service failed, the NIC drivers weren't installed, or DHCP assigned a different address. What's the most likely cause and the quickest way to regain remote control without redoing the install?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last six installs I keep losing time because I guess partition schemes and network setup…
Become — change the pattern
+Reinstalling because of mismatched network and partition decisions
Over the last six installs I keep losing time because I guess partition schemes and network setup during handoffs. I want a habit that prevents rework and saves on-console fixes. What checklist or preflight habit should I adopt so installs succeed first time and I can hand them to DB and ops without coming back?
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.