Umbrella sources: one score, many senders
Scripts and Hazel are umbrellas: one parent score covers every sub-source underneath. How that works, how deep it goes, and how it differs from UniFi grouping.
Endless possibilities, by design
Tempo doesn't know about your specific tools. It reads the JSON payload you send and adapts the UI to whatever fields are there. The sender writes the buttons.
Why we call them scores
A note on the musical name behind Tempo's building blocks, and the scores shipping at launch.
What Tempo is not
Before launch, a clear look at what Tempo deliberately isn't, and why that matters.