RCA-2026-03-27-001: Prevention

Preventive Measures

Short-term (This week)

Action Owner Status

Add btc/bt1/bts aliases to ~/.zshrc

Evan

[ ] Pending

Practice bluetoothctl commands 3x

Evan

[ ] Pending

Add to codex/networking/bluetooth.adoc

Evan

[ ] Pending

Long-term (This quarter)

Action Owner Status

Create Bluetooth section in Terminal Mastery curriculum

Evan

[ ] Pending

Add wofi/rofi Bluetooth menu

Evan

[ ] Pending

Detection

How was it detected?

  • Manual observation - urgently needed device, couldn’t recall syntax

Detection Gap

Could have been prevented with pre-configured aliases. The gap was not in detection but in preparation.

Lessons Learned

What went well

  • Asked for help immediately instead of wasting time

  • One-liner pattern (awk + xargs) was effective

  • Recognized opportunity for systematic improvement

What could be improved

  • Need shell aliases for infrequent but critical operations

  • Bluetooth CLI should be in the mastery curriculum

  • Consider wofi/rofi integration for GUI fallback

Key Takeaways

  1. Infrequent != unimportant - Operations needed under pressure require MORE preparation, not less

  2. awk pipeline pattern - command | awk '{print $2}' | xargs -I{} command2 {} solves many "connect to thing" problems

  3. Trust + auto-connect - Trusted devices should reconnect automatically; if they don’t, the issue is elsewhere

  4. Non-interactive mode - bluetoothctl doesn’t require the interactive shell; single commands work

Related