The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The new firewall rule to allow TCP 5432 from 10.20.0.0/16 to db02 needs to be applied. Add the…
Execute — do the immediate task
+The new firewall rule to allow TCP 5432 from 10.20.0.0/16 to db02 needs to be applied. Add the rule, then send the change summary to Kamal in SecOps and Nina, the database lead, asking them to confirm connectivity tests by Friday. Check the rule order and that there are no conflicting deny rules before applying.
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 propose this firewall change to SecOps, make it easy to approve: show the exact traffic…
Improve — make it easier to accept
+Before I propose this firewall change to SecOps, make it easy to approve: show the exact traffic flow and justification, put the risk and compensating controls up front, and flag any existing deny rules or rule order issues that would make the change ineffective or raise concerns for a reviewer in security.
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 added a rule to allow TCP 5432 to db02 from the new subnet but Nina reports clients still can’t…
Decide — diagnose the stuck moment
+I added a firewall rule and connections still fail
I added a rule to allow TCP 5432 to db02 from the new subnet but Nina reports clients still can’t connect. I told Kamal and paused further changes, but I don’t know if the rule order, a missing NAT, or a host-level firewall is blocking traffic. What is the likeliest cause and what should I check first to restore connectivity without opening extra 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 approving firewall tweaks that then break application connectivity or leave shadow rules…
Become — change the pattern
+Firewall changes repeatedly break expected flows
We keep approving firewall tweaks that then break application connectivity or leave shadow rules that confuse on-call. Where are we bleeding time and trust in how we manage firewall rules, and which single habit should we change to reduce rework and accidental outages?
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.