Sticky notes are not a control plane
A sticky note next to the trackpad is honest about one thing: you do not trust yourself to remember the order. It is not honest about whether the queue is healthy, which port Vite stole, or what Cursor should restart.
Rig's job is the repeatable stack. Groups, preferred scripts, health, ports, logs. The sticky note can stay for the weird client deploy you do twice a year.
What belongs on the board
- Processes you start more than twice a week
- Sidecars that die quietly (queue, Vite, proxy)
- Anything an agent should be allowed to inspect
What can stay a note
- One-off
artisanexperiments - Temporary tunnels you tear down after the call
- Passwords (never on a sticky note either — use your vault)
If the morning ritual is already muscle memory, keep it until it breaks once on a travel day. Then put it on the board. First 10 minutes is the short path.
Related
- Running local dev processes: from terminal tabs to a process manager
- Procfile validator
- Procfile guide: syntax, process types, and running it locally
- Run multiple dev servers locally: which approach fits
- Morning boot without six tabs
- Teleport a project between Macs
- Procfile projects
- Health-aware start order
- Processes table
- Journal
https://userig.app/blog/sticky-notes-are-not-a-control-plane